Replace ScreenshotOne?
KINDA · weekend projectA competent coding agent can build a useful self-hosted screenshot endpoint around Playwright in a weekend. Matching ScreenshotOne's reliable browser fleet, proxy locations, stealth behavior, maintained blocking rules, videos, and production edge-case handling is a much larger infrastructure product.
Build me a self-hosted website screenshot API to replace ScreenshotOne for personal use. Requirements: - Node 22 + Fastify + Playwright (Chromium) + better-sqlite3, one process, no queue system. - GET /take?url=&format=png|jpeg|webp|pdf&width=&height=&full_page=&delay_ms= renders the page in a pooled Chromium context and returns the image bytes directly. - POST /take accepts raw HTML or Markdown in the body and renders that instead (Markdown through marked into a plain template). - Auth is one API key from .env, checked on every request; 401 without it. - Cache by hash of the normalized options: metadata in SQLite, files under data/cache/, with a cache_ttl option and a fresh=true bypass. - Block ads and cookie banners the honest way: load EasyList and the "I don't care about cookies" filter list at startup, apply them via request interception, plus a small CSS hide-list for common consent overlays. Do not promise it catches everything. - Hard 15-second navigation timeout, one retry, then a JSON error with the reason; never a hanging request. - Concurrency capped at a small context pool (default 2) with an in-memory queue, so the box does not fall over. - Out of scope: proxies and IP locations, stealth evasion, scrolling video capture, GPU rendering, dashboards, usage billing. That fleet is the paid product. - README: npx playwright install chromium, .env keys, Chromium memory expectations, and a one-line warning that hostile sites will beat this build.
$ open in your agent (prompt prefilled, you press enter) or copy it raw
They want a screenshot API that stays reliable across hostile, slow, dynamic, and consent-heavy sites without operating Chrome/Chromium workers, updating blocking rules, managing proxies, or debugging browser failures.
xmanaged browser capacity, rate limiting, and high availability
xmaintained ad, cookie banner, chat widget, and popup blocking rules
xresidential proxies, selectable IP locations, and stealth tuning
xscrolling screenshots, video generation, and GPU rendering
xproduction support for difficult sites and browser edge cases
No mature prior art is listed for this record.
What does the ScreenshotOne verdict mean?
The core job looks buildable, with meaningful gaps: managed browser capacity, rate limiting, and high availability, maintained ad, cookie banner, chat widget, and popup blocking rules. Read the full tradeoff list before committing. This research record is not a hosted IVCIFY tool.
What price does this directory record show for ScreenshotOne?
The directory records $17/month for Basic, checked 2026-08-03. Verify the source before making a purchase decision. This reference stays outside retail Stack Math unless current matched evidence supports the comparison.
What do I lose by replacing ScreenshotOne?
Honestly: managed browser capacity, rate limiting, and high availability; maintained ad, cookie banner, chat widget, and popup blocking rules; residential proxies, selectable IP locations, and stealth tuning; scrolling screenshots, video generation, and GPU rendering; production support for difficult sites and browser edge cases. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to ScreenshotOne?
This record does not list mature open-source prior art. The build prompt remains available as a research starting point.