Website Screenshot
Capture screenshot of any website by URL. Preview how sites look on different devices. Download screenshots in high quality
A screenshot of a website at a specific viewport size is useful for: SEO meta-image previews, marketing materials, archival ("what did the site look like in May 2026"), responsive design audits across devices. This tool fetches and renders any public URL, captures at any viewport size (mobile, tablet, desktop, ultrawide), and saves PNG / WebP / PDF. Useful when "open in browser, F12, set device emulation, screenshot" is the wrong number of steps and you want one button.
What it captures
- Full page — entire content top-to-bottom, scrolling capture. For long pages, results in tall images (thousands of pixels).
- Viewport only — visible portion at the specified viewport size. Like a real browser at that size.
- Specific element — a single CSS-selected element. Useful for capturing one component without the surrounding chrome.
- After delay — wait N seconds before capturing. For pages with lazy-loading images, animations, or JavaScript rendering that needs to settle.
- Mobile viewport — emulate phone screens (iPhone 16: 393×852, Pixel 8: 412×915, smaller for legacy testing).
- Tablet viewport — iPad: 1024×1366. Surface: 1280×800.
- Desktop / ultrawide — 1920×1080, 2560×1440, 3840×2160.
Working example: a responsive design audit
Input
Audit how a homepage looks across breakpoints before launch
Output
Captures: Mobile (iPhone 16): 393×852 — header, hero, CTA visible above fold Mobile landscape: 852×393 — squashed; CTA below fold Tablet (iPad): 1024×1366 — sidebar appears Desktop (1280): 1280×800 — full nav, hero with image Desktop (1920): 1920×1080 — wider hero, maintains 1280-content + side padding Ultrawide (2560): 2560×1440 — same as 1920 but more padding Review reveals: - "Sign up" CTA falls below fold on mobile landscape — fix layout. - Hero image stretches awkwardly between 1280 and 1920 — set max-width. - Mobile portrait works well; tablet sidebar looks crowded. Export all as PDF for the design review meeting.
Capturing at multiple breakpoints once is more reliable than asking the team to "test responsiveness" on devices they may not have. Combine with browser devtools emulation for issues that screenshots cannot show (touch interactions, scroll behavior).
Common use cases
- Open Graph / Twitter Card preview images — capture the page at 1200×630 for og:image. Tools like vercel/og generate these dynamically; for static sites, manual capture works.
- Archive / historical record — "what did our pricing page look like before the redesign". Capture and store.
- Marketing materials — screenshots of your product in marketing decks, case studies, blog posts.
- Competitor monitoring — capture competitor pages on a schedule to spot copy / pricing changes.
- Bug reports — show how a page rendered in your environment. Pair with browser/OS info.
- SEO audits — capture how Google likely sees the page (no JS, mobile viewport, slow network).
When to reach for this tool
- You need a screenshot of a website at a specific viewport size without manually emulating in devtools.
- You are creating Open Graph images for blog posts or social-share metadata.
- You are documenting a third-party website (competitor, reference) and want a clean capture.
- You are doing a responsive design audit and want comparable captures across breakpoints.
What this tool will not do
- It will not capture content behind a login. The tool sees the public web; authenticated content requires the tool to log in (which has security and consent implications).
- It will not run client-side authentication or cookies. For sites that gate content behind cookies, the screenshot is the logged-out / first-visit state.
- It will not handle every JS-rendered SPA perfectly. Some pages take longer than the wait timeout to fully render; complex animations may capture mid-frame.
- It will not screenshot internal / private sites. The renderer must be able to reach the URL; intranet sites need a local capture tool or screen recorder.
For internal / authenticated content, capture locally with the screen-recorder tool or browser devtools "Capture full-size screenshot" command. Local capture bypasses any remote-rendering service entirely.
Frequently asked questions
Why does my screenshot look different from my browser?
The renderer uses a specific browser version with default fonts and zero personalization (no cookies, extensions, or user settings). Differences with your view come from: cached versions, signed-in state, A/B test buckets, browser extensions affecting rendering. For testing public state, the screenshot tool is more representative; for "how this user sees it", capture locally.
Can I screenshot a page that requires login?
Not directly. Public renderers do not have your credentials. Options: (1) use local capture (browser screenshot tool, screen recorder); (2) configure an authenticated renderer with stored cookies (some commercial services like Browserless support this); (3) use a Playwright / Puppeteer script with login logic.
How fast is the capture?
Typical: 3-10 seconds. Includes URL fetch, page render, screenshot. Slow sites or pages with heavy JS can take 20+ seconds. Some renderers wait for "page load" event; others wait for "network idle"; the latter handles JS-heavy SPAs better.
Why does my Open Graph image look pixelated on Facebook?
Facebook recommends 1200×630 minimum for high-resolution previews; smaller images are upscaled and look blurry. Always capture at 2x what you need; some platforms (Twitter) accept up to 1280×1280.
Can I capture animated SVG / video / canvas content?
Screenshots are single frames. Canvas drawings, SVG animations, video players all render to a single static frame. For animated capture, record the screen (see screen-recorder tool).
Is there a rate limit on captures?
Most browser-based renderers cap at 5-50 captures per minute to protect infrastructure. For batch screenshot generation (hundreds at once), use a dedicated API service (Browserless, ScreenshotOne, ApiFlash) or run Puppeteer locally.
Related tools
Create beautiful code screenshots with syntax highlighting. Carbon-like code images with themes. Free online code snippet to image converter
Generate SEO meta tags, Open Graph, Twitter Cards with live preview. Optimize website metadata for search engines and social sharing
Convert images between PNG, JPEG, and WebP formats. Batch conversion with quality control. Free online image format converter
Record your screen, browser tab or webcam directly in browser. No installation required. Export to WebM or GIF. Free online screen capture tool
Published · Updated · E-Utils editorial team