Skip to main content

​
Ad Blocking

Block advertisements from appearing in your screenshots using built-in ad blocking technology.

​
How it works

When enabled, the blocker intercepts network requests and blocks known ad servers and tracking scripts before they load.

​
Basic usage

bash
curl "https://api.domshot.com/shot?key=YOUR_API_KEY&url=https://example.com&blockAds=true" \
  --output screenshot.png

​
Benefits

  • Cleaner screenshots - Remove distracting advertisements
  • Faster loading - Fewer resources to download
  • Consistent results - Avoid dynamic ad content variations
  • Privacy-focused - Blocks known tracking scripts
Ad blocking may cause layout shifts or broken elements on websites that rely heavily on ad revenue. Test thoroughly before using in production.

​
When to use ad blocking

Use caseRecommended
Documentation screenshotsYes - cleaner appearance
E-commerce sitesMaybe - may affect layout
News sitesYes - removes ads/clutter
Social mediaYes - improves consistency
Testing web appsNo - may break functionality

​
Combining with other blocking

Ad blocking can be combined with banner and tracking blocking:
bash
curl "https://api.domshot.com/shot?key=YOUR_API_KEY&url=https://example.com&blockAds=true&blockBanners=true&blockTracking=true" \
  --output screenshot.png
See also:

​
Parameters

ParameterTypeDefaultDescription
blockAdsbooleanfalseEnable ad blocking using prebuilt filters

​
Performance impact

Ad blocking has minimal performance overhead:
  • Initial filter loading: ~50-100ms (one-time per request)
  • Network request blocking: Reduces overall page load time
  • Memory usage: Slight increase for blocker instance
For pages with heavy advertising, enabling ad blocking often results in faster screenshots and smaller file sizes.