Website Screenshot Tool: Desktop and Mobile Captures

Capture a public website viewport and export a real image

Website Screenshot Tool requests a remotely rendered image of a public page, then previews that image in your browser. It offers a desktop viewport of 1280 by 720 pixels and a mobile viewport of 375 by 667 pixels. These settings describe the requested browser viewport. They do not guarantee that the target serves the same layout, content or consent state that you see in your own browsing session.

Choose this tool when you need a quick visual reference for a permitted public page: a design review, a landing-page comparison or a support report. The capture is an image, not an editable DOM export, browser session recording or archival proof of every page state. It does not authenticate to a website, click through a dialog, scroll through a workflow or capture an entire application interaction.

Step-by-step capture and export

Enter the public page address in the existing URL field. An address without a scheme receives HTTPS. Submit with Take Snapshot and wait for the preview. The interface accepts standard HTTP or HTTPS public-domain URLs and rejects credentials, IP literals and nonstandard ports. Correct the address locally before retrying; changing a private IP to a public-looking hostname does not make private content appropriate to capture.

Capture uses the documented DOM-loaded navigation mode with an automatic 1.5-second settling wait. This avoids waiting indefinitely for network-idle on pages with persistent requests, but does not guarantee that late content is ready. Select the viewport before submitting. Changing the URL or viewport clears the prior capture so an old preview cannot be mistaken for a new request. Output File Format controls the downloaded file, while the screenshot itself comes from the remote renderer. Choose PNG for lossless encoding or JPEG for a usually smaller file, then use Download Website Screenshot after a readable preview is available.

The download creates bytes in the chosen format. A PNG source selected for JPEG export is decoded and re-encoded as image/jpeg, with transparent areas composited over white. Merely renaming a PNG to a .jpg filename would be incorrect. JPEG can introduce compression artifacts in text, icons and sharp edges; keep PNG when those details matter. The download notification means the browser received a file, not that a particular operating-system folder was verified.

Original viewport comparison exercise

For a repeatable exercise, use a public test page that you control with a short heading, two paragraphs and a responsive two-column section. Capture it in desktop mode and record the visible heading and column arrangement. Next select mobile mode and capture the same address. The expected desktop request specifies width 1280 and height 720; the mobile request specifies width 375 and height 667 and requests mobile behavior.

On a responsive test page, the mobile image should usually show the columns stacked. If it does not, inspect the page’s own media queries, viewport declaration and capture response before declaring the tool defective. User-agent handling, cached content and the provider’s rendering environment can affect the result. Compare the images visually and inspect their actual pixel dimensions rather than assuming a viewport setting proves the final image size.

Export the same successful preview once as PNG and once as JPEG. Open both files in an image viewer and inspect their file types. Both should depict the same capture; the JPEG should have JPEG bytes and the PNG should have PNG bytes. File sizes vary with image content, so a smaller JPEG is a practical tendency, not a guaranteed ratio or a quality score.

What is sent and what remains local

The capture request goes directly to Microlink with your public URL and selected viewport settings. Microlink renders the target remotely and returns image data. The target website can observe that remote visit. Avoid signed links, access tokens in query strings, private dashboards and pages containing information that should not be shared with a capture service. This page does not ask for your account password or send your local browser cookies to the target.

After a successful request, preview decoding and PNG or JPEG export happen locally in the browser. The preview uses an object URL backed by image data in memory; a page reload discards that application state. Site-wide analytics, infrastructure logs and the provider’s own processing are separate from this local image conversion. Read the SimplyUtils Privacy Policy and the provider’s terms when deciding whether a particular public page is appropriate.

Failure cases, budgets and troubleshooting

A capture expires after 45 seconds rather than leaving the controls waiting indefinitely. The returned image must be nonempty, use an accepted PNG, JPEG or WebP media type and match its file signature. The image budget is 20 MiB, at most 8192 pixels on either side and 16 million pixels in total. Oversized or undecodable responses produce an error and leave download unavailable; an error page is not saved as a screenshot.

If capture fails, first open the exact URL normally and confirm it is publicly reachable. Then try a short page you own, check the network error and wait before retrying a rate-limited provider. Login requirements, bot challenges, blocked requests and provider quota can prevent capture even when the page opens for you. Do not repeatedly resend a private or blocked address in an attempt to bypass those controls.

If the capture is readable but looks incomplete, check whether the missing material requires a click, late script execution, a location-specific response or scrolling. A viewport image does not promise full-page coverage. If export fails after preview, keep the readable preview and retry the format conversion in a supported browser. Include the public test URL, selected viewport, chosen format and exact error when reporting a problem; omit credentials and sensitive query parameters.