Screenshot API
API for converting URLs and HTML into screenshots and PDFs with ad blocking and CSS injection
Gallery
About Screenshot API
Screenshot API is a service that renders URLs or raw HTML into image and PDF outputs via a simple API. You send a request with a URL or HTML payload, and it returns a PNG, JPEG, WebP, or PDF. The use cases are familiar to anyone who has built link previews, generated invoices, captured pages for testing, or needed social cards at scale. Instead of running your own headless browser infrastructure, you call an endpoint and get back a file.
The rendering engine runs on Playwright and Chromium, which means it handles modern JavaScript, CSS, and complex layouts the way a real browser would. You can inject custom CSS or JavaScript before the capture, so if you need to hide a cookie banner, apply branding, or modify the page in any way, you have that control. Ad and tracker blocking is built in, which cleans up captures and speeds up rendering by skipping requests to known ad networks.
For partial captures, you can target a specific element using a CSS selector rather than screenshotting the entire viewport. That is useful when you only need a component, a widget, or a particular section of a page. Webhook callbacks handle asynchronous results, so if you are capturing at scale and do not want to block on each request, you can fire off jobs and receive the outputs later.
Pricing follows a credit model. The free tier gives you 100 renders per month with no card required, which is enough to test the integration and handle light usage. Paid plans start at $19 per month for 2,000 renders and scale up to $299 per month for 75,000 renders. If you need volume beyond that or prefer to buy once rather than subscribe, one-time credit purchases are available for agencies and project-based work. Credits never expire, so you are not penalized for uneven usage patterns.
The API comes with client libraries for cURL, Python, Node.js, and Go, so integration into most stacks is quick. Documentation covers the basics, though for niche scenarios you may need to experiment with timing, viewport settings, and injection order to get consistent results across different page types.
The target audience is developers and agencies who need programmatic screenshot or PDF generation without maintaining their own browser farm. Link thumbnail generators, visual regression test suites, invoice and receipt pipelines, and social card services are typical fits. If you are already running Puppeteer or Playwright locally and want to offload that to a hosted service, Screenshot API can handle the infrastructure so you do not have to.
Where it stands out is the flexibility. Ad blocking, CSS injection, element targeting, and webhook callbacks are all first-class features rather than afterthoughts. The credit model with no expiration also means you are not locked into a monthly burn if your usage spikes and dips. For teams that need reliable rendering at scale without the ops burden, it is a straightforward choice.
Key Features
- Render URLs or raw HTML to images and PDFs
- Ad and tracker blocking built in
- CSS and JavaScript injection before capture
- Element-specific captures via CSS selector
- Webhook callbacks for async results
- Credits that never expire
Pros & Cons
What we like
- Free tier with 100 renders per month
- Flexible output formats including WebP and multi-size PDFs
- One-time credit purchases available for agencies
- Client libraries for Python, Node, Go, and cURL
Room for improvement
- Complex pages may require tuning timing and viewport settings
- Higher volume plans get expensive at scale
- No self-hosted option for teams that need on-prem
- Documentation covers basics but not every edge case
Frequently Asked Questions
What is Screenshot API?
Is Screenshot API free?
What languages does the API support?
Can I capture just part of a page?
Best For
Featured in
Alternatives to Screenshot API
View all1Lookup
Real-time data verification API for phone, email, IP, and domain validation to fight fraud
Kevin Gabeci
Solo developer building web apps, cozy browser games, and AI creator toolkits.

Codedex
A gamified, story-driven platform that teaches Python, web dev, and more like an RPG quest
Hack2hire
Practice real SDE interview questions from top tech companies with expert worked solutions
Reviews (9)
Good, with a few caveats
Three months of Screenshot API later, here is what holds up. Their take on credits that never expire is genuinely good. What stands out is how little babysitting it needs. It fits well for capturing pages for visual regression testing. It would be a five if not for documentation covers basics but not every edge case.
Exactly what I needed
Screenshot API has quietly become part of my daily flow. Their take on credits that never expire is genuinely good. It handles the boring parts so I can focus on the work that matters. No regrets so far.
Pulled its weight from week one
Found Screenshot API on a Show HN thread and I am glad I clicked. Got real value out of client libraries for python, node, go, and curl. What stands out is how little babysitting it needs. Found it works best for rendering invoices and receipts as pdfs. Would sign up again without thinking twice.
Pulled its weight from week one
Have been running Screenshot API for a while, here is where I land. Got real value out of render urls or raw html to images and pdfs.
Genuinely impressed
Hadn't planned on switching, but Screenshot API was hard to ignore. Their take on element-specific captures via css selector is genuinely good. No regrets so far.
Decent with some rough edges
Tried Screenshot API on a side project first, then rolled it out everywhere. Their take on webhook callbacks for async results is genuinely good. Setup was painless and I was productive the same day. Mostly using it for generating link previews and social cards at scale. It would be a five if not for higher volume plans get expensive at scale. Glad I made the switch.
Quietly excellent
Tried Screenshot API on a side project first, then rolled it out everywhere. Their take on ad and tracker blocking built in is genuinely good. It slotted into my routine without much fuss. It fits well for building a screenshot gallery of competitor sites. Easy yes for anyone weighing the same trade offs.
Finally something that fits
Tried Screenshot API on a side project first, then rolled it out everywhere. Where it really wins is render urls or raw html to images and pdfs. It fits well for generating link previews and social cards at scale. Easy yes for anyone weighing the same trade offs.
Finally something that fits
Three months of Screenshot API later, here is what holds up. It just works, day after day, without surprises.
Related Tools
Kevin Gabeci
Solo developer building web apps, cozy browser games, and AI creator toolkits.

Coolify
Self-hostable, open source alternative to Heroku and Netlify

Warp
The modern terminal reimagined with AI and collaboration

Bolt.new
Prompt-to-deployed full-stack app inside the browser