Distill.io review: features, limits, and who it suits
Distill.io monitors pages and selected content for changes. Here’s how its local and cloud checks, alerts, limits, and trade-offs fit different needs.
Distill.io is a website-change monitoring service: it checks a page or selected content on a schedule, compares the result with an earlier check, and can alert you when a change matches your conditions. Choose a local monitor when you need frequent checks or the site blocks remote requests and you can keep a device running. Choose a cloud monitor when checks must continue while your device is off and the site is reachable from Distill’s servers. Distill is for detecting changes; for a clean image or PDF capture of a page, ScreenshotNeo is the alternative to try first, with consent banners, popups, and chat widgets removed before capture and billing limited to clean shots.
1. What Distill does
Distill opens the monitored source, reads its content, compares it with the previous version, optionally evaluates conditions, and triggers configured actions. A monitor can watch an entire page or a selected portion. Selection and refinement options documented by Distill include XPath, CSS, regular expressions, and JavaScript. Conditions can filter notifications, for example by checking for text or a numeric range.
Documented monitor types include web pages, PDFs, JSON, Word documents, XML, feeds, uptime, and sitemaps. Notifications can use email, SMS, mobile push, Discord, Slack, Microsoft Teams, or other integrations through webhooks. Distill is available as a web app, browser extensions, phone apps, and desktop apps; its documentation describes desktop apps as public beta, so check current availability before relying on them.
2. Local and cloud monitors
| Consideration | Local monitor | Cloud monitor |
|---|---|---|
| Where a check runs | Your browser or desktop device | Distill’s servers |
| Device required | Yes; browser or app must be running | No |
| Check frequency | Documentation lists intervals as low as 5 seconds | Flexi web-app monitors have a 2-minute minimum |
| Check quota | Documentation describes local checks as unlimited | Checks count against plan resources |
| Best fit | Frequent checks or pages that reject cloud requests | Always-on monitoring without a running local device |
| Other details | PDF and XML supported; proxies not supported | PDF and XML supported; proxy support depends on plan/configuration |
Local checks depend on the device and relevant browser or app staying available. Background checks work only for static pages according to Distill’s documentation; pages rendered dynamically may need a different local mode or cloud configuration. Cloud checks continue with your device off, but may fail when a site blocks Distill’s remote requests. A proxy or local monitoring may help, but neither guarantees that every site can be monitored.
3. Selection, schedules, conditions, and alerts
Monitor only the content that matters
Whole-page monitoring is quick to set up but can produce noise from navigation, timestamps, ads, or rotating recommendations. Select the relevant element when possible, then inspect change history to make sure the selection captures the intended content. Advanced selectors and conditions can be powerful but may require adjustment when a site changes its structure.
Choose a schedule that matches the decision
Distill documents interval and random schedules, a live mode for local monitors when a page updates with JavaScript, and cron-style schedules for enterprise use. Local monitors can use shorter intervals; use the slowest cadence that still gives you enough time to act. Very frequent checks consume cloud resources quickly and can send excessive alerts if the monitored region is noisy.
Filter notifications
Conditions support tests such as contains, does not contain, starts with, ends with, and is empty, with AND/OR combinations documented for more involved rules. For example, monitor a product price region but notify only when the extracted value falls below a threshold. Keep the condition tied to the selected content and review the recorded values when an alert seems incorrect.
4. Distill plan limits and cost
Distill’s official pricing and features pages showed the following limits when accessed on October 3, 2026. Treat them as a dated snapshot, not a guarantee: plan allowances and prices can change, and the research available for this review did not establish stable current prices to quote.
| Plan information shown | Allowance |
|---|---|
| Free local monitors | 25 |
| Free cloud monitors | 5 |
| Free cloud checks | 1,000 per month |
| Free alert frequency | 6 hours |
| Free email alerts / phone push notifications | 30 / 100 |
| Free devices | 2 |
| Paid monthly cloud checks shown | 30,000; 100,000; and 200,000+ on Flexi |
Distill defines one cloud check in ten-second units: a check taking up to ten seconds counts as one, and a check taking more than ten but less than twenty seconds counts as two. Unused resources expire at the end of the billing period. Flexi usage beyond reserved resources is billed at period end. Review the live plan page and the limits shown for your account before choosing a plan.
Estimate cloud usage as monitors × checks per monitor × checks per month, then allow for checks that take longer than ten seconds, since those can consume multiple units. Also compare alert quotas, device limits, change history, and macro needs, not just the raw check count. Local checking can avoid cloud check quotas, but its practical cost is keeping a device available.
5. Who Distill suits
- Deal, ticket, or appointment watchers: a selected page element and a useful alert channel can help surface a change without repeatedly checking manually.
- Researchers and teams tracking updates: conditions can narrow alerts for competitive intelligence, legislative changes, grants, or policy content.
- People who need checks while away: cloud monitors run without a personal device left on, if the target allows Distill’s cloud requests.
- People who need fast or site-specific checks: local monitoring offers shorter intervals and can work when cloud requests are blocked, provided the local device stays active.
- Developers monitoring structured data: Distill documents JSON and other non-page monitor types, useful when the source is a feed, document, or endpoint rather than a visual page.
It is a less suitable fit if you need guaranteed access to a site that blocks the chosen execution path, cannot keep a local device running but need more checks than a cloud allowance supports, or need a screenshot rather than change detection.
6. Setup checklist
- Decide whether the check must continue while your computer is off. If yes, start with cloud; otherwise consider local.
- Add the page or supported source and select the smallest stable region that answers your question.
- Run checks and inspect the captured content/change history before depending on alerts.
- Set a schedule that leaves enough time to react while avoiding unnecessary checks.
- Add conditions and alert actions, then verify that a real relevant change would satisfy the condition.
- Review monitor, check, alert, device, and history limits against your expected monthly use.
- Revisit the monitor if the site changes its layout, blocks requests, or begins returning errors.
7. Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| Cloud monitor cannot load the page | The site blocks remote requests, or the request times out | Try a supported proxy configuration or switch to local monitoring. A proxy is not a guarantee. |
| Local monitor stops checking | The browser/device or desktop app is not running | Keep the relevant local device active, or use a cloud monitor if the source permits it. |
| Dynamic page content is missing | Content appears after JavaScript runs; a static/background check may not see it | Use an execution mode/configuration suited to dynamic content, or try local monitoring and verify the captured result. |
| Too many alerts | The selection includes changing noise or the condition is too broad | Narrow the selected region and refine conditions; inspect stored values when tuning. |
| No alert after a change | Wrong region, condition not met, action missing, or alert quota/channel issue | Inspect the detected content and condition evaluation, confirm an alert action is configured, and check account quotas. |
| Cloud usage is higher than expected | Checks take longer than ten seconds and consume multiple units | Check request duration and monthly cadence; account for ten-second billing units and reduce unnecessary frequency. |
| Unsupported type or validation error | Source format is unsupported, stale configuration, or extracted value fails validation | Confirm the documented monitor type and update selection/validation rules to match the returned data. |
Distill maintains a troubleshooting guide for check errors and a separate guide for missing alerts; use those pages for error-specific steps.
8. Performance, reliability, and trade-offs
Check frequency is not the same as alert latency: a change can only be detected after a successful scheduled check, and notification delivery follows detection. A shorter interval reduces the maximum wait for the next check in principle, but cloud quotas, site response time, blocking, and alert conditions all affect the practical result. The reviewed material does not establish independent accuracy or uptime measurements, so do not treat a configured schedule as a delivery guarantee.
For reliability, monitor a stable content region, avoid selectors tied to fragile layout details, test conditions against actual changes, and periodically review error status and history. For important workflows, consider whether a missed check or delayed alert has a cost that requires a separate fallback. Check the site’s access rules and avoid a cadence that places unnecessary load on it.
9. Screenshot alternative: ScreenshotNeo
Distill answers “what changed?” ScreenshotNeo answers “what does this page look like?” It is a website screenshot API and MCP server from Yorker Media. Use it when your task is producing a PNG, JPEG, WebP, or PDF capture rather than tracking future changes. It removes cookie/consent banners, newsletter popups, and chat widgets before capture; those steps can be disabled. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify page verdict and billing status with headers.
For a one-request capture, see the ScreenshotNeo API documentation. Replace YOUR_API_KEY with an account key:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo also has an MCP server with take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. Every feature is on every plan: 1,000 shots/month free with no card; paid plans start at $5 for 3,000 shots, followed by Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000. Yearly billing gives two months free. Sign up for 1,000 free screenshots a month with no card.
10. FAQ
Can Distill monitor only part of a page?
Yes. It supports visual selection and documented selector/refinement methods including XPath and CSS.
Does my computer need to stay on?
Only for local checks. Cloud checks run on Distill’s servers.
Can Distill monitor PDFs and JSON?
Those are among its documented monitor types. Some monitor types have plan or execution-mode constraints, so confirm current documentation for the source you need.
Is Distill a screenshot API?
No. It monitors content for changes. For a screenshot or PDF capture through an API, consider ScreenshotNeo.
