Website screenshot generator

Capture any public web page as an image, full length or just the first screen, at desktop, laptop, tablet or phone size. Cookie banners and ads can be hidden before the shot.

  • Rendered in real Chrome, with JavaScript
  • PNG, JPEG or WEBP download
  • No signup needed
Ready

Screenshot

Enter a URL to start

Size —
File —
Device
—
Capture
—
Took
—
  1. URL
    Waiting for input
    The page you entered
  2. Rendered by
    ApiFlash
    Chrome in the cloud
  3. Viewport
    —
    Width the page is laid out at
  4. Image
    —
    Sent to your browser, not stored

Your screenshot

Enter a URL above and choose a device to see the screenshot here, with its size and file weight, ready to download.

Fair-use limit: 10 screenshots per hour and 30 per day for each visitor IP address. Respect copyright and site terms before publishing a screenshot.

What a website screenshot shows, and what it can't

The image is a real browser render, but from a visitor with no history, no login and no location of yours.

A real browser, not a drawing of the HTML

The page is opened in Chrome, scripts run, fonts and images load, and only then is the picture taken. What you get is what a first-time visitor on that screen size would see.

The viewport decides the layout

Responsive sites rearrange themselves by width. A 390-pixel capture shows the phone menu and stacked columns; 1920 pixels shows the full desktop layout. Height matters only for the first-screen option.

Full page versus first screen

Full page scrolls the page and stitches its whole length into one image, which is ideal for archives and reviews. First screen shows exactly what a visitor sees before scrolling, which is ideal for judging the hero section.

Why it can differ from your own view

Sites personalise by cookies, login, country and experiments. The capture comes from a data centre as a brand-new visitor, so prices, languages, pop-ups and even whole sections can differ.

Devices and formats at a glance

What each preset and file type is, and when to choose it.

SettingWhat it isBest for
Desktop, 1920 × 1080 The most common desktop screen size. Landing pages, presentations, above-the-fold reviews.
Laptop, 1440 × 900 A typical laptop width, often below a site's widest layout. Checking layouts that change between large and small desktops.
Tablet, 820 × 1180 A portrait tablet in the iPad Air range. Navigation and grid changes at tablet breakpoints.
iPhone, 390 × 844 The CSS size of recent standard iPhones. Mobile layouts, menus and stacked content.
Android, 360 × 800 One of the most common Android CSS widths. Checking that nothing overflows on narrower phones.
PNG Lossless: sharp text, larger files. Interface reviews, bug reports, documentation.
JPEG or WEBP Compressed at quality 85: much smaller files. Long pages, sharing, photos and previews.

How this tool works

What happens between entering a URL and downloading the image.

  1. The URL is checked

    Only public http and https addresses on ports 80 and 443 are accepted. Private, internal and localhost addresses are refused before anything is sent.

  2. The capture is requested

    Our server sends the URL and your settings to ApiFlash with our API key. Your IP address and browser details are not sent.

  3. Chrome renders the page

    ApiFlash opens the page in Chrome at the chosen size, waits for it to load plus your extra wait time, scrolls it to load lazy images for full-page shots, and hides cookie banners and ads if you asked.

  4. The image comes back through us

    The finished image is streamed through our server to your browser without being saved here.

  5. You preview and download

    See the screenshot with its size and file weight, then download it. Nothing is added to a gallery or history.

What this tool does, and what it doesn't

A plain list, so you know exactly what to expect.

This tool does

  • Render public pages in Chrome with JavaScript
  • Capture the full page or the first screen
  • Use five desktop, tablet and phone sizes
  • Scroll to load lazy images before a full-page shot
  • Hide cookie banners and block ads on request
  • Download as PNG, JPEG or WEBP

This tool does not

  • Log in or capture private pages
  • Get past captchas or bot protection
  • Record video or clicks
  • Capture localhost or internal addresses
  • Grant any right to reuse what you capture
  • Store screenshots on our server

Where your data goes

The URL and your capture settings are sent to ApiFlash, which loads the page from its own servers and returns the image. ApiFlash keeps a cached copy for up to one hour, under its own privacy policy. The image passes through our server to your browser and is not saved here, and the website you capture sees ApiFlash, not you. Like any website, our server may keep normal access logs, as described in our privacy policy.

Curious about the rendering service? ApiFlash documents how its Chrome-based captures work.

Read the ApiFlash docs

Why your screenshot might look unexpected

The six surprises people run into most, and what to do about each.

Blank areas in a full-page shot

The site loads images only when they come into view or after an animation. Choose a 5-second wait and capture again.

A security check instead of the page

Bot protection such as Cloudflare or a captcha blocked the screenshot service. Some sites cannot be captured remotely.

A different language or cookie notice

The page was opened from a data centre with no cookies, so it may look like a first visit from another country.

Mobile layout looks slightly different

The capture uses the phone's CSS width at a 1:1 pixel ratio. Fonts and some device-only features can differ from a real phone.

A huge file for a long page

Full-page PNGs of long pages can reach tens of megabytes. Switch to JPEG or WEBP for a file that is easy to share.

The capture timed out

Very slow or heavy pages can take longer than the service allows. Try the viewport-only option or a lighter page.

Questions about website screenshots

Who actually takes the screenshot?

ApiFlash, a screenshot service that runs Google Chrome in the cloud. Our server sends it the URL and your settings, ApiFlash loads the page and returns the image, and we pass it straight to your browser. The website you capture sees a visit from ApiFlash, not from you.

Why are some images or sections blank?

Many pages load images only when you scroll to them, or fade content in with animations. The tool scrolls the page before a full-page capture, but very slow or interaction-based content can still be missing. Choose a longer wait time and try again.

Why does the screenshot look different from what I see?

The page is loaded from a data centre with no cookies, no login and no browsing history, often from another country. Sites can show different content, prices, languages or banners to that visitor. Bot protection can also show a check page instead of the real one.

Which image format should I choose?

PNG keeps text and interface edges sharp but makes large files, especially for long pages. JPEG and WEBP are much smaller and are fine for photos and sharing. For a very long page, choose JPEG or WEBP.

Can I capture a page behind a login, localhost or a staging site?

No. The screenshot service can only open public pages that need no login. Private, internal and localhost addresses are refused before any request is made. For those, use your browser's own full-page screenshot feature.

Can I use screenshots of other websites?

A screenshot copies someone else's design, text and images, which are usually protected by copyright. Personal reference, internal reviews and bug reports are generally fine, but check the site's terms and get permission before publishing or using a screenshot commercially.

Are my screenshots or URLs stored?

Not on our server: the image passes through to your browser and is not saved. ApiFlash keeps a cached copy for up to one hour so a repeat request is faster, under its own privacy policy. A hashed, temporary copy of your IP address is used for rate limiting and expires within 24 hours. Like any website, our server may keep normal access logs, as described in our privacy policy.