How to Capture a Website Screenshot with a Custom Wait Time in Screenshot.rocks

Short answer: Screenshot.rocks’ published guide describes URL capture, an optional mobile layout, and export, but does not document a custom wait-time setting. If a page needs extra time to render or you need a particular interactive state, capture it in a browser workflow that supports a delay, then import the image into Screenshot.rocks for framing and export. This is a finding about the documented guide, not a claim that no undocumented control exists.

What Screenshot.rocks documents

The documented online flow is for the first screen of a publicly reachable page. Enter a URL, optionally choose Mobile, capture, choose a frame and background, and export. The guide says you may omit the https:// prefix.

1. Open the Screenshot.rocks editor.
2. Enter the public website address under “Or capture a website.”
3. Select Mobile for the phone layout, or leave it unselected for desktop.
4. Press Capture.
5. Choose a frame style and background, then export.

The guide describes the capture as the first screen—the portion visible before scrolling—not a full-page image. Its published specifications are desktop 1440 × 800 at 2× density (2880 × 1600 output pixels) and mobile 375 × 812 at 3× density (1125 × 2436 output pixels). These are the service’s published specifications, not independent measurements.

How to capture after a custom wait

Use a browser capture workflow that explicitly supports a delay or a condition such as waiting for a selector. A fixed delay is useful for predictable animation or client-side rendering time; waiting for a selector is usually more reliable when you know which element marks readiness. Capture the desired viewport or full page, save the resulting image, and import it into Screenshot.rocks to apply its frame and background and export.

1. Open the page in a browser workflow where you can set a delay or wait condition.
2. Use the same viewport, browser state, and zoom you want represented in the final image.
3. Wait for the content you need. Prefer a specific readiness condition over an arbitrary long delay when available.
4. Capture the visible viewport, or a full-page image if that workflow supports it.
5. Save the screenshot and import it into the Screenshot.rocks editor for styling and export.

For a fixed delay, choose a duration long enough for the expected content to appear, then verify the captured image. Network speed and application behavior vary, so no single delay is right for every page. If the page exposes a reliable element only after rendering, wait for that element instead of adding increasingly long delays.

Choose the right capture path

Need	Suitable path	Important limit
Public page, first screen, no special wait	Screenshot.rocks URL capture	The documented flow does not show a wait control.
Delayed content or a specific UI state	Browser capture with a delay or readiness condition, then import	The capture workflow must support the required wait and state.
Logged-in content, localhost, or staging	Capture from a browser that can access the page, then import	Screenshot.rocks says its online server capture cannot see these pages.
Entire scrolling page	Use a browser workflow that supports full-page capture, then import	The guide describes online capture as the first screen; its extension captures the visible part of the current tab.
Site blocks automated browsers	Capture in a browser session the site permits, then import	The online server capture may not work for blocked automated browsing.

When online URL capture is not a fit

Screenshot.rocks says its online server capture cannot access content behind a login or local addresses such as localhost, and may not work on sites that block automated browsers. Its guide recommends capturing the page yourself for logged-in pages, a particular state such as an open menu or filled form, local or staging pages, and full-page images. The browser extension captures the visible part of the current tab; the guide does not describe it as a full-page capture mechanism.

For interactive states, prepare the state in the browser before capturing: sign in if authorized, open the menu, fill the form, or reach the desired route. Avoid including private data in an image you plan to share. After saving the image, use the editor for presentation rather than expecting the online URL capture to recreate that state.

Import, style, and export

Once you have the image, use the editor’s frame and background controls and export the result. The Screenshot.rocks homepage says images are processed in the browser and are not stored on its servers; its capture guide separately says server capture returns the image to the browser without storing it. If handling sensitive material, check the service’s current privacy information and avoid uploading or sharing content you are not permitted to disclose.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server for developers. Its capture options include a delay, selector wait, or network-idle wait, plus full-page capture, element capture, custom CSS and JavaScript, and device and viewport settings. See the ScreenshotNeo API documentation for request options.

curl -G "https://api.screenshotneo.com/v1/shot" \
  -d access_key=YOUR_API_KEY \
  --data-urlencode url=https://stripe.com \
  -d wait=3000 \
  -o shot.webp

The example requests a 3,000 millisecond wait. Replace the URL and set the wait option to the duration your page needs. The same API accepts the parameter names used by other screenshot APIs, which can make switching easier.

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={
        "access_key": "YOUR_API_KEY",
        "url": "https://stripe.com",
        "wait": 3000,
    },
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://stripe.com',
  wait: '3000',
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', new Uint8Array(await res.arrayBuffer()));

For AI-agent workflows, ScreenshotNeo also provides an MCP server with take_screenshot, get_page_info, and capture_pdf. Cookie and consent banners, newsletter popups, and chat widgets are removed before capture; each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers report the page verdict and billing status. The free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots.

Sign up for 1,000 free screenshots a month, with no card required.

Troubleshooting

Symptom	Likely cause	What to do
The page is captured before content appears	The documented online flow does not expose a documented custom wait setting, or the selected delay is too short.	Capture in a workflow with an explicit delay or readiness condition; wait for a meaningful element when possible.
A login page appears instead of the target content	The online server capture cannot see the authenticated browser session.	Capture from a browser already signed in, then import the image.
Localhost or staging URL cannot be reached	The server-side capture cannot access your local network or private environment.	Capture from a browser with access to that environment.
Only the top portion is present	The online capture is documented as first-screen capture; the extension captures the visible tab.	Use a browser workflow that explicitly supports full-page capture.
A menu or form state is missing	The URL capture does not reproduce your manually prepared interactive state.	Set up the state in your browser before capturing.
Automated capture is blocked	The site may reject automated browsers.	Use a browser session the site permits, subject to the site’s rules, then import the result.
Image looks soft or has the wrong dimensions	Viewport and pixel density affect output size and sharpness.	Choose the intended desktop or mobile layout, and confirm the published dimensions meet your output needs.

Performance, reliability, and cost

A fixed wait adds that time to every capture, even when a page loads sooner. A readiness condition can reduce unnecessary waiting, but it depends on choosing a condition that reliably indicates the content is ready. Full-page captures and pages with heavy client-side rendering can take longer and may produce different results as content changes. For repeatable captures, use a consistent viewport, state, and wait rule, and keep a copy of the output when you need an auditable record.

The Screenshot.rocks guide and homepage describe a free browser-based editor and online capture flow; consult the current site for applicable limits or terms. ScreenshotNeo’s stated plans are Free: 1,000 shots per month, Starter: $5 for 3,000, Growth: $15 for 15,000, Pro: $39 for 60,000, Scale: $99 for 250,000, and Business: $249 for 1,000,000. Yearly billing gives two months free, and every feature is on every plan. Cache hits are not billed; response headers identify billing and page verdicts. Consider caching for repeated captures and using a wait duration appropriate to the content so jobs do not spend time waiting after they are ready.

FAQ

Does Screenshot.rocks document a custom wait time?

The published guide does not show a delay, selector wait, or timing parameter. That describes the guide’s documented workflow, not every possible undocumented capability.

Does the online capture make a full-page screenshot?

The guide describes the first screen before scrolling. Use a separate browser capture workflow for a full-page image, then import it for styling.

Can I use a screenshot of a logged-in page?

Yes, by capturing it from a browser with authorized access and importing the resulting image. The guide says the online server capture cannot see content behind a login.

Are uploaded images stored by Screenshot.rocks?

The homepage says editor images are processed in the browser and not stored on its servers; the guide says server-captured images are returned to the browser without storage.

Sources

• Screenshot.rocks: Website Screenshot Generator — documented URL flow, first-screen scope, layout specifications, and capture limitations.
• Screenshot.rocks homepage — browser-side image processing and storage statement.