A LITTLE HELP. A LOT DONE.
Good tools.
Great flow.

Your shortcut to the everyday. Create, convert, calculate,
and get back to what you love.

✓ Free to use✓ No sign-up✓ 500+ possibilities
Developer

Page Screenshot Service

Capture full-page or viewport screenshots of any public URL as PNG or JPG using real browser rendering.

Loading interactive tool…

About this tool

Page Screenshot Service sends a publicly reachable HTTP(S) URL to the screenshot backend, which captures it with a desktop, tablet, or mobile viewport. Choose a viewport-only or full-page capture and PNG or JPG output. The target must be reachable by the server and may render differently when it requires login, blocks automation, or depends on private network access; the screenshot is a capture of the returned page, not a guarantee of how every crawler sees it.

Why use it

  • Real browser rendering means JavaScript, fonts, and CSS all execute — no blank or broken pages.

  • Three device presets let you test mobile, tablet, and desktop layouts in one tool.

  • Full-page capture grabs content below the fold that viewport screenshots miss.

  • PNG and JPG format choice balances quality versus file size for your use case.

  • Private IP blocking prevents misuse for internal network reconnaissance.

  • No software install — capture any page in seconds from any device.

How to use

  1. Enter the full URL of the page you want to screenshot (must start with https:// or http://).
  2. Click a device preset chip — Desktop, Tablet, or Mobile — to set the viewport dimensions.
  3. Toggle 'Full page' on to capture the entire scrollable page, or leave it off for viewport only.
  4. Choose PNG for lossless quality or JPG for a smaller file.
  5. Click Screenshot. A spinner indicates the capture is in progress (usually 5-10 seconds).
  6. Preview the screenshot inline, then click Download to save it to your device.

When it helps

  • Checking how a webpage looks on mobile without opening DevTools and toggling responsive mode
  • Generating screenshots for client presentations or bug reports.
  • Archiving the visual state of a page before making changes.
  • Testing OG/social preview images by seeing what a crawler would render.
  • Creating thumbnails or preview images for documentation.

Examples

Desktop full-page screenshot

Input
URL: https://www.example.com
Device: Desktop (1280×800)
Full page: ON
Format: PNG
Expected result
PNG file approximately 1280px wide by full document height (e.g. 4200px tall), showing the page from top to footer with all CSS rendered.

Mobile viewport-only screenshot

Input
URL: https://news.ycombinator.com
Device: Mobile (375×812)
Full page: OFF
Format: JPG
Expected result
JPG file 375×812 px showing the mobile layout at the top of the page, ideal for sharing in chat as a quick visual reference.

OG preview check

Input
URL: https://blog.example.com/post-slug
Device: Desktop (1280×800)
Full page: OFF
Format: PNG
Expected result
1280×800 PNG showing the page hero, used to verify what social-media crawlers (Twitter, Facebook, LinkedIn) approximate when generating link previews.

Tips

  • Use the Mobile preset (375×812 — iPhone 13 Pro size) when checking responsive layouts, not the Tablet preset.
  • Full-page mode triggers a virtual scroll to ensure lazy-loaded images and infinite-scroll first-batch content render.
  • JPG at default quality is fine for most screenshots; switch to PNG only when you need pixel-perfect text rendering.
  • If the page has cookie banners, the screenshot will include them — there is no way to dismiss interactive prompts.
  • Pages with auth walls return the login screen since the headless browser has no session cookies.
  • For viewport-only shots, content below the fold is not captured — toggle full-page on for marketing pages and blogs.
  • Repeated captures of the same URL may take longer if the site has weak caching or many third-party scripts.

Frequently Asked Questions

Which rendering engine does this use?
The server uses Playwright with Chromium as the primary renderer. If Playwright is unavailable, it automatically falls back to Puppeteer (also Chromium-based).
How long does a screenshot take?
Typically 5-15 seconds depending on page complexity and network speed. The tool waits for 'networkidle' so ads, fonts, and lazy-loaded images have time to render.
Can I screenshot a page that requires login?
No — the headless browser opens the page without any cookies or session state. Only publicly accessible pages can be captured.
What is the maximum viewport size?
Width is capped at 2560px and height at 4096px for safety. The three device presets cover the most common use cases.
Does full-page capture work on infinite scroll pages?
It captures content that is rendered on initial load and networkidle. Infinite scroll content that requires user interaction will not be included.
Can I screenshot localhost or private IP pages?
No — private IP ranges and localhost are blocked to prevent SSRF attacks. Only publicly routable URLs are accepted.

Explore the category

Lighthouse Lite Audit Run a Lighthouse-style performance, SEO, accessibility, and best practices audit on any public webpage using Google PageSpeed Insights. Website Status Checker Check whether any website or URL is up or down and see its HTTP response code, response time, and server headers. HTTP Headers Checker Inspect response status and headers from public HTTPS origins Responsive Breakpoint Previewer Preview any URL at common responsive breakpoints (mobile, tablet, desktop) side by side or individually in an iframe. SERP Preview Tool Desktop and mobile style snippets with soft character guides. Broken Link Checker Find broken and dead links on any webpage. Live status updates and CSV export included.
How Browsers Render a Web Page: From HTML to Pixels A browser takes HTML, CSS, and JavaScript and turns it into pixels. The steps between those two points — parsing, layout, painting, composit May 2026 · 11 min Lighthouse and Core Web Vitals: What Each Score Actually Measures LCP, INP, CLS, TTFB — the alphabet soup of web performance. We explain what each metric measures, what passes the bar, and how to actually m Mar 2026 · 9 min Understanding the Critical Rendering Path and How to Optimize It The critical rendering path is the sequence of steps a browser must complete before showing the first pixel. Optimizing it is one of the hig May 2026 · 10 min

Glossary

Headless Chromium
Google Chrome's rendering engine running without a visible UI window, used here on the server to render pages and capture pixels programmatically.
Playwright
Microsoft's browser automation library that drives Chromium, Firefox, and WebKit headlessly with a unified API; the primary engine for this tool.
Puppeteer
Google's earlier browser automation library, also driving headless Chromium; used as a fallback when Playwright is unavailable.
Viewport
The visible browser window dimensions in CSS pixels; the screenshot's width and height when full-page mode is off.
Full-page capture
A screenshot of the entire scrollable page from top to bottom, achieved by virtually scrolling and stitching slices together.
networkidle
A Playwright/Puppeteer wait condition that resolves when there have been no network connections for 500 ms — ensures async content finishes loading before capture.
PNG (Portable Network Graphics)
A lossless raster format ideal for screenshots with sharp text, UI elements, and solid colours; larger files than JPG.
JPG (JPEG)
A lossy raster format that compresses photos and gradients efficiently but introduces artifacts in text-heavy screenshots.
Device pixel ratio (DPR)
The ratio of physical to CSS pixels — Retina displays have DPR 2 or 3. The default capture uses DPR 1 unless otherwise configured.