PNG is the right format when you need lossless quality: UI snapshots, documentation images, visual archives, or anywhere text must stay crisp. Screenshotty renders the page in a real headless Chrome browser and returns the PNG directly, so you can embed the endpoint in an <img> tag or fetch it from your backend.
Unlike DIY headless-browser setups, there is nothing to host, patch, or scale. Pass the URL, get the PNG.
Try the free Website Screenshot toolGET request — embed directly in HTML
Node.js
Everything You Need, Built In
Lossless PNG output
Sharp text and exact colors at any viewport size, up to 4K (3840×2160) with retina device_scale_factor support.
Transparent backgrounds
Set transparent_background=true to strip the page background — ideal for capturing UI components or rendering assets.
Clean captures by default
Built-in ad blocking and cookie-banner blocking so your PNGs show content, not consent pop-ups.
Full page or any element
Capture the entire scrollable page with full_page=true, or a single element with a CSS selector.
Frequently Asked Questions
How do I convert a URL to PNG with an API?
Send a GET request to https://api.screenshotty.link/api/v1/screenshot with your target url and format=image/png. The API renders the page in headless Chrome and returns the PNG. Get a free API key at screenshotty.link — 100 screenshots per month, no credit card required.
Can I get a PNG with a transparent background?
Yes. Pass transparent_background=true (PNG only) and the page background is removed — useful for capturing isolated components, charts, or rendering image assets.
Is there a free tier?
Yes. Screenshotty includes 100 screenshots per month for free with no credit card required. Paid plans start at $9/month for 2,500 screenshots, with pay-as-you-go overage at $0.004 per screenshot.
Does it render JavaScript-heavy pages?
Yes. Every capture runs in a real headless Chrome browser, so single-page apps, lazy-loaded images, and dynamic content render exactly as they do for a real visitor. You can also wait for a specific ready event or add a custom delay with wait_ms.