Grab a picture of any live page
Paste a URL, pick a size, hit Capture. A few seconds later you get a PNG or JPEG of the page exactly as a browser sees it. No extension to install, no Chrome dev tools, no fiddling with your OS screenshot key and then cropping the result.
Here’s the part that matters: this isn’t a thumbnail pulled from some cache. The page renders in real headless Chrome on Toolsvu’s server, runs its JavaScript, loads its fonts and images, and then gets photographed. So a single-page app that paints its content after load shows up correctly, not as a blank shell.
How to use it
Type or paste the address. Skip the https:// if you want — “stripe.com” works fine, the tool adds the scheme for you. Then choose how the page should be framed:
- Desktop (1280x800) is the safe default for most sites.
- Laptop (1366x768) matches the most common laptop screen out there.
- Tablet (768x1024) and Mobile (375x667) show you the responsive layout, the way a phone or iPad would.
- Or punch in your own width (320 to 1920) and height (240 to 4000) if none of the presets fit.
Flip on Full page when you want the whole scrollable document, header to footer, not just what fits above the fold. Height gets measured for you in that mode. Pick PNG for crisp text and sharp edges, JPEG when you’d rather have a smaller file and don’t mind a little compression. Capture, then download.
What’s going on under the hood
The server spins up a headless Chromium instance, sets the viewport to your chosen dimensions, navigates to the URL, waits for the page to settle, and renders the frame to an image. Full-page captures stitch together everything from the top of the document to the bottom, which is why a long article or a tall landing page takes a bit more time than a single viewport.
Most captures land in the 5 to 15 second range. A heavy page with lots of images, web fonts, and third-party scripts sits at the slower end. That’s normal — the tool is waiting on the actual site, not on Toolsvu.
Where this comes in handy
You’re filing a bug and the layout looks broken on a certain width. Capture it at that exact viewport and attach the image to the ticket — way clearer than “it looks weird on my screen.” Designers grab reference shots of competitor pages. Marketers pull a clean screenshot of a landing page for a deck without launching the site live in front of an audience. And if you’re documenting a release, a before-and-after pair of full-page captures tells the story at a glance.
One honest limitation: anything behind a login won’t render, since the capture browser arrives as a fresh anonymous visitor with no session. Same goes for pages guarded by aggressive bot protection — you might get a challenge screen or a partial render instead of the real content. And for safety, private and localhost addresses are refused, so you can’t point it at internal network resources.
FAQ
Does it work on single-page apps and JavaScript-heavy sites?
Yep. The page runs in real Chrome and its scripts execute before the shot is taken, so React, Vue, and similar apps render their actual content rather than an empty container.
Why was my URL rejected?
Private IPs, localhost, and internal-network hostnames are blocked on purpose to prevent the server reaching things it shouldn’t. Public URLs go through fine. If a public site still fails, it likely timed out loading — the error message will say so.
Can I screenshot a page that needs a login?
Nope. The capture browser shows up with no cookies or session, so anything gated behind a sign-in renders as the logged-out view, or not at all.
PNG or JPEG — which should I pick?
PNG keeps text and lines sharp and is the better choice for UI and documentation. JPEG produces a smaller file with slight compression, which is fine for quick previews or when file size matters.
Why is the capture taking so long?
Big full-page grabs and slow, asset-heavy sites both add time. The browser waits for the real page to finish loading, so a 5 to 15 second wait is expected, and longer pages can run past that.
What’s the largest page I can capture?
Custom width tops out at 1920px and height at 4000px for a fixed viewport. Full-page mode measures the document for you, so a tall page captures top to bottom without you setting a number.