ScreenshotMachine Screenshots Look Blurry: How to Improve Image Quality
Fix soft ScreenshotMachine captures by checking dimensions, zoom, device, page readiness, format and cache settings—in that order.
If a ScreenshotMachine screenshot looks blurry, first check the requested width and height, then zoom and device settings. Also confirm the page finished loading and that you are not viewing an older cached capture. ScreenshotMachine documents widths from 100 to 1920 pixels, heights from 100 to 9999 pixels or full, and zoom from 10% to 400%. Its default dimensions are only 120 × 90 pixels, which can make a request that relies on defaults look small or soft.
These settings control capture size and rendering. They cannot restore detail missing from the page’s original images. ScreenshotMachine’s documentation describes zoom as useful for high-resolution screenshots and gives 200% as an example that produces an image twice as large as a 100% capture. That is a larger output, not a promise of additional source detail.
1. Check the requested dimensions
Start with the actual pixel dimensions of the downloaded image and compare them with the size at which you plan to display it. A small capture enlarged in a page, slide, or design file will look soft. ScreenshotMachine documents a default size of 120 × 90 pixels, a maximum width of 1920 pixels, and numeric heights up to 9999 pixels. Use full when you need a full-page capture.
Choose dimensions for the intended output rather than automatically requesting the maximum. For example, a thumbnail does not need the same dimensions as a large presentation image. If you need a larger image, request larger dimensions and inspect the returned file’s dimensions before changing other settings.
2. Set zoom and device deliberately
ScreenshotMachine accepts zoom values from 10% through 400%. Its documentation gives zoom=200 as an example that makes the screenshot twice as large as a zoom=100 capture. Try a higher zoom when the output needs more pixels, then verify the resulting image dimensions and page layout. The API documentation says zoom is ignored for screenshots smaller than typical device dimensions.
Device emulation affects how a modern page renders. ScreenshotMachine documents desktop, phone, and tablet; its examples include a desktop viewport of 1024 × 768, phone at 480 × 800, and tablet at 800 × 1280. A page can select different layouts or images for different viewports, so match the device and dimensions to the version you intend to capture.
3. Allow the page to finish loading
A screenshot taken while images, fonts, or animations are still loading can look incomplete. The ScreenshotMachine API’s default delay is 200 ms, and the documented range reaches 10,000 ms. For long pages with images or animations, its documentation recommends considering a delay of 2000 ms or more.
Increase delay only when the page needs time to settle. Waiting can let late content appear; it is not a resolution or sharpening control. If the page loads content only after scrolling, clicking, or another interaction, a longer delay may not be enough to trigger that content.
4. Compare formats without changing other settings
ScreenshotMachine documents JPG, PNG, and GIF output. The reviewed documentation does not establish one format as universally sharpest or provide a screenshot quality parameter. To diagnose a format difference, capture the same URL with identical dimensions, device, zoom, delay, and freshness settings, changing only the format. Compare the actual files at the same display size.
Do not assume that changing to PNG will fix every soft capture. If the source page serves a small image, or the screenshot is requested at too few pixels, changing format does not create missing detail.
5. Rule out a cached capture
An older capture may not reflect your latest settings or the current page. ScreenshotMachine’s cacheLimit setting controls the acceptable age of a cached image from 0 to 14 days; cacheLimit=0 requests a fresh screenshot. Its pricing FAQ says screenshots are cached for 14 days and cached loads are not billed.
6. Troubleshoot in a controlled sequence
- Inspect the downloaded file dimensions. If they are smaller than expected, set explicit width and height instead of relying on defaults.
- Match the device and viewport. Capture the desktop, phone, or tablet layout you actually need.
- Try a higher zoom. Check the returned dimensions and remember that zoom does not recover detail absent from the page’s source images.
- Wait for late content. Increase delay when images or animations are visibly unfinished, then compare the result.
- Compare formats. Hold all capture settings constant and change only JPG, PNG, or GIF.
- Request freshness. Set
cacheLimit=0when you need to rule out an older cached image.
| Symptom | Likely setting to inspect | What to try |
|---|---|---|
| Image is tiny or becomes soft when enlarged | Width and height | Request explicit dimensions suited to its display size; defaults are 120 × 90. |
| Output is larger but details still look soft | Zoom and source image | Try a higher zoom, then check whether the page itself uses a low-resolution image. |
| Mobile page looks wrong or blurry | Device and viewport | Choose the intended device and matching dimensions. |
| Images are missing or partly rendered | Delay and page loading | Allow more time for content to load; delay does not sharpen an already-rendered image. |
| Changes do not appear in the capture | Cache age | Set cacheLimit=0 to request a fresh screenshot. |
Runnable request examples
Use the request format and parameter names from your ScreenshotMachine account and API documentation. The examples below show the settings to compare; confirm the exact endpoint and authentication method for your account. Keep the URL and all other parameters fixed when diagnosing one setting at a time.
cURL
curl -G "SCREENSHOTMACHINE_API_ENDPOINT" \
--data-urlencode "url=https://example.com" \
--data-urlencode "dimension=1024x768" \
--data-urlencode "device=desktop" \
--data-urlencode "zoom=200" \
--data-urlencode "delay=2000" \
--data-urlencode "cacheLimit=0" \
--output screenshot.pngPython
import requests
params = {
"url": "https://example.com",
"dimension": "1024x768",
"device": "desktop",
"zoom": 200,
"delay": 2000,
"cacheLimit": 0,
}
response = requests.get("SCREENSHOTMACHINE_API_ENDPOINT", params=params, timeout=90)
response.raise_for_status()
with open("screenshot.png", "wb") as image_file:
image_file.write(response.content)Node.js
const params = new URLSearchParams({
url: 'https://example.com',
dimension: '1024x768',
device: 'desktop',
zoom: '200',
delay: '2000',
cacheLimit: '0',
});
const response = await fetch(`SCREENSHOTMACHINE_API_ENDPOINT?${params}`);
if (!response.ok) {
throw new Error(`Screenshot request failed: ${response.status} ${response.statusText}`);
}
const image = new Uint8Array(await response.arrayBuffer());
await import('node:fs/promises').then(({ writeFile }) => writeFile('screenshot.png', image));Replace the placeholder endpoint and any parameter names with those specified for your ScreenshotMachine API plan. The API documentation lists width and height as separate controls; if your account expects separate parameters instead of a combined dimension, use its documented syntax. For a full-page capture, use the documented full-page option and consider extra delay for a long page.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. One GET request returns a PNG, JPEG, WebP, or PDF. Cookie banners are accepted and removed before capture, along with known consent platforms, newsletter popups, and chat widgets. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers say what happened. Its MCP server lets AI agents use screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.
See the ScreenshotNeo API documentation. Example request:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSign up for 1,000 free screenshots a month, with no card.
Performance, reliability, and cost notes
- Performance: Larger dimensions and longer waits can affect how much data is returned and how long you wait for it. Use the smallest output size that meets the display need, and increase delay only when the page has late content.
- Reliability: Keep URL, viewport, zoom, delay, format, and cache freshness consistent when comparing results. This makes it easier to identify which setting changed the output.
- Cost: ScreenshotMachine’s pricing FAQ says cached loads are not billed. The dossier does not provide enough pricing detail to estimate the cost of uncached captures, so check your plan before running large batches.
FAQ
Why does my ScreenshotMachine screenshot look blurry?
Common settings to check are small output dimensions, zoom, device emulation, page readiness, and cache freshness. The particular cause depends on the request and the page.
Does a 200% zoom guarantee sharper detail?
No. ScreenshotMachine documents that zoom can produce a larger screenshot, but a larger output cannot restore detail missing from the page’s source images.
Should I always use PNG?
No universal format ranking is established by the documented material. Compare formats using the same capture settings and the actual output files.
What should I send support if the image is still soft?
Include the request settings and the resulting file so the capture dimensions, device, zoom, delay, format, and cache behavior can be reviewed together.
