Troubleshooting
Daily limit reached
Free accounts get 400 server-side detections per rolling 24 hours, Pro 5,000 plus 300 rechecks and 600 classifier calls. Past the limit, on-device checks keep running.
Updated
The limits
| Free | Pro | |
|---|---|---|
| Server-side detections (text and image batches) | 400 per rolling 24 hours | 5,000 |
| Model rechecks | none | 300 |
| Classifier calls | none triggered (cached results still shown) | 600 |
Signed-out use is limited per hashed IP address rather than per account, which on a shared network can run out sooner. Limits are rolling windows, not calendar days.
What happens past the limit
The API answers with a rate-limit error and the extension carries on with what it can do locally: writing-pattern analysis and same-origin provenance reads. Circles for stripped images stop appearing until the window moves on. Nothing is queued or lost; content is simply re-checked next time it is seen.
Reducing usage
- Turn off Scan this site on feeds you do not care about.
- Add busy domains to the deny list in the options page.
- Batches are already limited to content near the viewport, so scrolling slowly uses fewer checks than jumping around.
Getting more
Pro raises the detection limit to 5,000 per day and adds rechecks and classifier calls. See Free versus Pro. We may adjust limits to protect the service, with 30 days' notice of reductions to paid tiers except to prevent abuse.