site-shot.com

A website screenshot API is a hosted service that renders a URL on its own servers and returns an image file over HTTP. You send a request with the page address and your output preferences, and you get back a PNG, JPEG, or WebP — no browser window, no manual clicking. You should use one when screenshots need to happen repeatedly, on a schedule, or inside another program; you should skip it and use a free online tool when you just need one image right now.

How a screenshot API differs from an online screenshot tool

Both approaches can capture the same page, but they solve different problems.

Site-Shot illustrates the split directly: its free online tool captures any URL as PNG, JPEG, or WebP with no signup and no API key, while the API runs on the same Chromium engine and requires an account plus email confirmation to issue a key. The rendering is identical — the difference is who presses the button.

What to check before you integrate one

Rendering and output format

Confirm which formats you get and whether the service supports lossless output. Site-Shot returns PNG, JPEG, or WebP, with WebP described as lossless.

Full-page height limits

This is the most common surprise. Site-Shot captures full-page and scrolling screenshots up to 20,000 px, but WebP output stops at 16,383 px — anything taller keeps only its top 16,383 px. If your pages are long (infinite-scroll feeds, documentation dumps), decide up front whether you need a taller format or whether you will stitch segments.

Viewport and device emulation

Check whether you can set width, height, zoom, and browser size, and whether mobile and tablet presets exist. Site-Shot exposes custom width/height/zoom plus named presets for desktop resolutions and specific phones and tablets, which matters if you are checking responsive layouts rather than just archiving a page.

Proxies and geolocation

If you need to see what a page looks like from another country — localized pricing, regional banners, consent flows — the service must route through that region. Site-Shot offers country selection with a direct-connection default and additional countries on paid plans, so verify that your target country is actually available on the tier you intend to use.

Page cleanup

Ads and cookie banners can cover the content you are trying to capture. Site-Shot advertises ad and cookie-popup removal as a built-in option; if your target sites are ad-heavy or show consent modals, test this before committing, since it changes what the image contains.

Typical use cases

• Automated monitoring — capture a page on a schedule and compare against the previous run to detect layout or content changes.
• Thumbnails and previews — generate link previews or gallery images without a human opening each URL.
• Visual regression testing — render the same page after each deploy and diff the images.
• Reports and archives — attach a dated screenshot to a report or store evidence of a page state.
• Localized captures — pull the same URL through different countries to compare regional versions.

What to prepare before integrating

1. An account and API key. Site-Shot requires creating an account and confirming your email before you receive a key. Budget for that step; it is not instant.
2. Your request parameters. At minimum the target URL, plus the viewport size, output format, and any options like full-page, country, or cleanup. Decide these before writing code so you are not debugging rendering and parameters at the same time.
3. A plan for large images. Long pages produce large files. Check the height limit for your chosen format and decide whether you need to cap, crop, or split.
4. Error handling. Pages time out, block requests, or render differently than expected. Treat a failed capture as a normal outcome, not an exception.
5. Storage and naming. Decide where images land and how you will identify them later — by URL, timestamp, or both.

When not to use an API

If you need a handful of screenshots, a one-off image for a document, or a quick look at how a page renders, the free online tool is faster: no account, no key, no code. Reach for the API when the capture has to be repeatable, unattended, or embedded in something else.

Open Site-Shot in your browser, paste the target URL, adjust the capture options, and download the image. No account, API key, or credit card is required for the online tool. You can capture PNG, JPEG, or WebP, choose a desktop or mobile viewport, take full-page screenshots, remove ads and cookie banners, and route the request through a specific country. The same Chromium engine also powers the Site-Shot screenshot API if you later need automation.

Step-by-step: capture a screenshot in the browser

1. Open the tool. Go to site-shot.com and find the "Take a website screenshot online" form.
2. Enter the URL of the page you want to capture.
3. Set the viewport. Pick a preset (for example Desktop 1920 × 1080, iPhone 16 Pro, or iPad Air 11-inch) or enter a custom width, height, and zoom.
4. Choose image options. Select the output format and, if needed, a scale for the image size.
5. Decide on full-page capture. Leave it off for a viewport-sized shot, or enable scrolling to capture the whole page.
6. Optional cleanup and localization. Turn on ad and cookie-banner removal, and select a country if you need a localized version of the page.
7. Generate and download the resulting image.

The expected result is a rendered image of the live page as the tool's Chromium browser sees it — not a cached thumbnail.

Output formats and the size limits that matter

Full-page screenshots are supported up to 20,000 px. The WebP ceiling is the one to watch: if a page is taller than 16,383 px, a WebP capture keeps only the top 16,383 px. For very long pages, use PNG or JPEG instead of WebP.

Viewport and device emulation

The tool ships with desktop presets (1280 × 1280, 1440 × 900, 1920 × 1080, and others) and mobile/tablet presets including recent iPhone, Samsung Galaxy, Google Pixel, and iPad models. Each preset carries its own width, height, and device pixel ratio, so a phone preset reproduces how the page lays out on that device rather than just shrinking a desktop view. If none of the presets fit, set a custom width, height, and zoom.

Localized captures with country selection

A country selector lets you request the page through a specific location — the tool lists the United States as a direct connection plus dozens of countries (Germany, Japan, Brazil, India, and many more). This is useful when a site serves different content, currency, or language by region. The listing shows 49 additional countries available with any paid plan, so the free country set is narrower than the full list.

Common problems and how to fix them

• Blank or partially rendered screenshot. The page may still be loading dynamic content. Try again, or capture a simpler URL to confirm the tool is working.
• Cookie banner or ad covering the page. Enable the "No ads / No cookie" option before generating.
• Truncated image on a very long page. You likely hit the WebP 16,383 px limit. Switch to PNG or JPEG, which support up to 20,000 px.
• Wrong layout. Check that the viewport matches the device you care about; a desktop preset will not show the mobile layout.
• Region-specific content missing. Select the relevant country instead of the direct connection.

When to move from the online tool to the API

The browser tool is the right choice for one-off or occasional captures. If you need to capture many URLs on a schedule, integrate screenshots into an app, or run the same capture repeatedly, the Site-Shot screenshot API uses the same Chromium engine. To use it, create an account, confirm your email to receive your API key, then request full-page screenshots from any URL. The API supports the same feature set described above — formats, device emulation, custom viewports, full-page scrolling, ad and cookie cleanup, proxy rotation, and geolocation. Pricing details are on the Site-Shot pricing page; the free online tool itself requires no signup, API key, or credit card.

A plain screenshot tool captures what's on your screen; a screenshot beautifier takes that capture and packages it into a share-ready visual with a background, shadow, tilt, and padding. If you only need to record information for yourself, a capture tool is enough. If the image will appear on social media, a landing page, a product listing, or a pitch deck, you want the beautifier step — otherwise your screenshot arrives as a flat rectangle competing with everything else in the feed. Screenshot Beautifier Pro is one example of the second category: a Chrome extension that handles capture and styling in one place, so you don't have to move the file into a separate design app.

The two jobs, separated

The confusion usually comes from the word "screenshot tool" covering both. They solve different problems:

Capture is about fidelity and speed. Beautify is about presentation. A capture tool that produces a pixel-perfect image still gives you a bare rectangle — fine for a bug report, weak for a Twitter post.

When a plain capture tool is the right call

Choose capture-only if:

• You're documenting a bug, a receipt, or a chat log for your own records.
• The image goes into an internal doc where nobody judges the framing.
• You need the raw pixels at exact scale with no added margins.
• Speed matters more than polish — one keystroke, done.

In these cases adding a gradient background is wasted effort. The information is the point.

When you need a beautifier

Reach for a beautifier when the screenshot is content — something a stranger will scroll past and decide whether to stop for. Common triggers:

• Posting a product screenshot to Twitter/X, LinkedIn, or a community.
• Putting UI shots on a landing page or in a feature section.
• Building a portfolio or case study where visuals carry the story.
• Creating a consistent look across many screenshots (same background, same shadow, same padding).

The tell is simple: if you'd otherwise open Figma, Canva, or Photoshop just to add a background and shadow, a beautifier does that job faster because it's built for exactly this one task.

What a beautifier actually gives you

Based on Screenshot Beautifier Pro's feature set, the capabilities that separate it from a capture tool are:

• Backgrounds — dozens of curated gradients plus solid colors, with a one-click shuffle to cycle combinations.
• Shadows — three styles with adjustable blur, spread, and opacity, so the screenshot appears to float.
• 3D tilt and padding — a subtle perspective tilt plus sliders for whitespace around the image.
• Watermark — an optional footer with your name or brand, toggleable.
• Export at 2× PNG — sized for 1:1, 16:9, 9:16, 4:5, or auto-fit, so you don't re-crop for each platform.

The 2× export and preset aspect ratios matter more than they sound. Re-cropping a screenshot for LinkedIn (1:1 or 4:5) versus a story format (9:16) is where most people lose an afternoon.

Input methods decide whether the workflow fits you

A beautifier is only convenient if it accepts the screenshot you already have. Screenshot Beautifier Pro supports four entry points:

1. Capture tab — screenshots the active browser tab directly.
2. Region select — drag to capture a custom area.
3. Upload image — drop in any existing screenshot or image file.
4. Paste from clipboard — takes whatever image is on your clipboard.

If you already have a folder of screenshots from another tool, methods 3 and 4 mean you don't have to re-capture anything — you just style what exists. If you're starting fresh, methods 1 and 2 keep it to one app.

The decision in one line

Use a plain capture tool when the screenshot is a record. Use a beautifier when the screenshot is a presentation. If you do both — capture for yourself, style for sharing — a tool that does both in one extension saves the export-import round trip.

One caveat worth checking before you commit: Screenshot Beautifier Pro's page markets it as free to add to Chrome, but the source material doesn't state whether any features sit behind a paid tier. If a specific gradient set or export option is essential to you, confirm that in the extension itself rather than assuming the free label covers everything.

To capture a full page website screenshot, you can either use a browser-based tool (paste the URL, pick a viewport, choose a format, and let it scroll the whole page into one image) or send a single request to a screenshot API when you need automation. Site-Shot offers both paths from the same Chromium engine: the online tool needs no signup or API key, while the API requires an account and email confirmation to get a key. The main constraints to plan around are height limits — full-page captures go up to 20,000 px, except WebP, which stops at 16,383 px.

Option 1: Capture a full page in the browser (no signup)

This is the fastest route for one-off screenshots. Everything runs in your browser, and per the site's own description there is no signup, no API key, and no credit card required.

1. Enter the target URL in the online tool.
2. Choose the capture mode — select the full-size / full-page option so the tool scrolls the entire page rather than grabbing only the visible viewport.
3. Set the viewport to match how you want the page to render (see the device table below).
4. Pick an output format: PNG, JPEG, or WebP.
5. Apply cleanup options if the page is cluttered — the tool can remove ads and cookie banners so they don't cover your capture.
6. Generate the screenshot and download the resulting image.

Expected result: one tall image containing the whole page, not just the top screen.

Viewport and device presets

The tool exposes both custom dimensions and named device emulation. Matching the viewport to the real audience matters, because responsive layouts change what a "full page" even looks like.

You can also set width, height, and zoom manually if none of the presets fit.

Format and height limits: the part that causes truncation

The most common "my screenshot is cut off" problem comes from format limits, not from the tool failing.

Practical rule: if the page is very long and you need WebP, expect the bottom to be dropped past 16,383 px. Switch to PNG or JPEG if you need the full height, or capture the page in sections.

Option 2: Automate with the screenshot API

Use the API when you need repeatable, batch, or scheduled captures rather than a one-off image.

1. Create an account on the site.
2. Confirm your email — the API key is issued after confirmation.
3. Send a single request with the target URL to capture a full-page screenshot.
4. Add parameters as needed: viewport size, device emulation, output format, proxy/geolocation, and ad or cookie-banner removal.

The API runs on the same Chromium engine as the online tool, so results should be consistent between the two. Code samples and API documentation are available on the site.

When the API is worth it over the browser tool

• You're capturing many URLs on a schedule.
• You need consistent viewports and formats across a set of pages.
• You need localized captures via proxy rotation and geolocation.
• You want clean images without ads or cookie popups at scale.

Getting clean, localized captures

Two features change the quality of the result more than most people expect:

• Ad and cookie-banner removal — without it, a consent dialog can sit on top of the page content in your screenshot, making the capture useless for documentation or comparison.
• Proxy rotation and geolocation — the tool lists a long set of country options (United States, Germany, Japan, Brazil, and many more). A page can serve different content, currency, or language by region, so a capture taken from the wrong location may not match what your users actually see. Note that a subset of countries is available on the free/direct connection, while additional countries require a paid plan.

Troubleshooting common failures

Choosing between the two paths

Use the online tool for one-off screenshots, quick checks, or when you don't want to create an account. Use the API when the capture needs to be automated, repeated, or run at scale with consistent settings. Both share the same engine and the same height and format limits, so the decision is about workflow, not image quality.

You can capture any URL as a PNG, JPEG, or WebP image directly in your browser using Site-Shot's online tool — no signup, no API key, and no credit card required. Paste the target URL, pick a format and viewport, and generate the screenshot. This works well for one-off captures, quick visual checks, and sharing a page as an image. If you need to run the same capture repeatedly or from code, the same Chromium engine is available as an API, which does require creating an account and confirming your email to get a key.

Taking a Screenshot in the Browser

The online tool follows a simple input → action → result flow:

1. Enter the target URL in the address field of the tool.
2. Choose your shot options — format, viewport size, and whether to capture the full page.
3. Generate the screenshot and download the resulting image.

Because the capture runs server-side on a Chromium engine, the result reflects what a real browser renders, not a simplified HTML preview. That matters for pages that depend on JavaScript, fonts, or lazy-loaded images.

Choosing an Output Format

The tool supports three formats, and the right choice depends on what the image is for:

If you need the tallest possible full-page capture, PNG and JPEG allow up to 20,000 px, while WebP stops at 16,383 px — anything taller keeps only the top portion.

Setting Viewport Size and Device Emulation

The viewport determines how the page lays out, which changes what the screenshot looks like. Site-Shot offers preset sizes plus custom width, height, and zoom:

• Desktop presets: 1280×1280, 1440×900, 1024×768, 1280×800, 1280×1024, 1366×768, 1920×1080
• Mobile presets: Samsung Galaxy A56, Galaxy S25, Galaxy S25 Ultra, Google Pixel 8/9/9 Pro, iPhone 14/16/16 Plus/16 Pro/16 Pro Max
• Tablet presets: iPad Air 11-inch, iPad Pro 12.9-inch

Pick a preset that matches your audience's device, or set a custom width and height if you need an exact dimension. Zoom lets you scale the rendered page before capture.

Capturing Full-Page Screenshots

Enable the full-size option to capture content below the fold. The tool scrolls the page and stitches the result into a single image. Two limits to keep in mind:

• PNG/JPEG: up to 20,000 px tall
• WebP: up to 16,383 px tall

If a page exceeds the limit, only the top portion is kept. For very long pages, consider capturing in sections or switching to PNG/JPEG for the extra height.

Cleaning Up Ads and Cookie Banners

The tool includes an option to remove ads and cookie-consent popups before capture. This is useful when you want a clean image of the page content without overlays that would otherwise cover the top of the screenshot. Enable it when the target site shows a consent banner or ad units that would obscure the layout.

Getting Localized or Region-Specific Captures

Site-Shot supports proxy rotation and geolocation, so you can capture a page as it appears from a specific country. The tool lists 49+ countries including the United States, United Kingdom, Germany, France, Japan, India, Brazil, and others. This matters when a site serves different content, pricing, or language based on visitor location. Note that some country options are marked with a lock icon, and additional countries are available with any paid plan.

Common Problems and How to Troubleshoot

• Blank or partially rendered screenshot: The page may still be loading dynamic content. Try again, or check whether the site blocks automated browsers.
• Truncated full-page capture: You've likely hit the height limit (20,000 px for PNG/JPEG, 16,383 px for WebP). Switch formats or capture in sections.
• Timeout: Very heavy pages or slow servers can exceed the capture window. Retry, or capture a lighter version of the page.
• Cookie banner still visible: Make sure the ad/cookie cleanup option is enabled, and re-run the capture.
• Wrong layout: The viewport size doesn't match the device you're targeting. Adjust the preset or custom dimensions.

When to Move to the API

The browser tool is the right choice for occasional, manual captures. Switch to the API when you need to:

• Capture the same page on a schedule or in bulk
• Integrate screenshots into an app, report, or monitoring pipeline
• Apply consistent settings across many URLs

The API uses the same Chromium engine and supports full-page capture, proxies, ad and cookie-banner removal, and the same format and viewport options. To get started, create an account and confirm your email to receive your API key, then send a single request per URL.