How to Add Authentication Cookies to a Screenshot.rocks Capture

Short answer: Screenshot.rocks’ documented workflow does not ask you to paste authentication cookies into the editor. Sign in to the page in your own browser, open the protected content, then click the Screenshot.rocks extension to capture the visible part of the active tab. For a full-page image, use your browser’s full-page screenshot feature and import that image into the editor. Screenshot.rocks is an editor for framing, styling, marking up, and exporting screenshots.

1. What “authentication cookies” means here

A site commonly keeps a login session in the browser after sign-in. The browser sends the relevant session data as you navigate, so a page can display account-only content. In Screenshot.rocks’ documented extension workflow, you establish that session by signing in through your browser. The extension captures the currently open tab; it is not a documented cookie-import interface.

This distinction matters: do not copy a session cookie from browser developer tools and paste it into the editor. A session cookie can grant access to an account, and the official Screenshot.rocks workflow reviewed for this guide does not describe manually entering cookie values.

2. Capture a login-protected page in Screenshot.rocks

1. Sign in normally. Use a browser profile where you are authorized to access the page. Complete any required MFA or consent steps yourself.
2. Open the target page. Navigate to the exact view you want in the mockup. Scroll and resize the browser so the desired portion is visible.
3. Capture the active tab. Click the Screenshot.rocks extension. Its guide says the captured image opens in the editor in a new tab.
4. Style and export. Choose an available browser frame or style, set a background, add markup if needed, then export the result.

The extension captures the visible portion of the tab, not the entire scrolling document. Anything below the current viewport will not be included in this capture.

For a full-page screenshot

Use your browser’s built-in full-page screenshot capability to capture the authenticated page, save the resulting image, then drop or import that image into the Screenshot.rocks editor for framing and markup. The browser stays responsible for the logged-in session; Screenshot.rocks edits the resulting image.

3. Visible-tab capture or full-page import?

Route	Page coverage	What you need	Best fit
Screenshot.rocks extension	Visible viewport only	The authenticated page open in a supported browser with the extension installed	A quick mockup of the current screen
Browser full-page screenshot, then import	Whole page, subject to the browser’s capture capability	The authenticated page and a browser full-page capture workflow	A long page or content below the fold

For either route, check the image before sharing it: account names, customer records, private URLs, notifications, and browser chrome can reveal information you did not intend to publish.

4. Privacy and safe handling

Screenshot.rocks says images are processed in the browser and are not stored on its servers. Its extension guide also says the captured image is sent to Screenshot.rocks to open in the editor and is not stored. Treat the screenshot as sensitive if it contains account or customer data, and capture only information you are allowed to access.

The Screenshot.rocks guide says its Chrome and Edge extensions request only the activeTab permission, allowing access to a tab when you click the extension button. Check the current extension listing and product documentation if you need to verify permissions before installing; browser and product details can change.

5. When a cookie-injection API is the right tool

If you need a server-side job to authenticate to a page without an already signed-in human browser, you need a different workflow: an API or controlled browser that explicitly accepts cookies or other authentication inputs. That is separate from Screenshot.rocks’ documented extension capture. Only send credentials to a service whose current documentation and retention terms you have reviewed, and use a narrowly scoped test account where possible.

For automated website screenshots, ScreenshotNeo is an API and MCP server that accepts custom cookies, headers, and authorization inputs. Its one-request API returns an image or PDF, and its response headers identify page verdict and billing status. This is useful when you want API-controlled capture rather than an image captured from your own authenticated tab.

Or skip the browser setup

ScreenshotNeo can capture a URL through one GET request. See the ScreenshotNeo API documentation for the current parameters. Set the cookie or authorization inputs your target site requires, and keep secrets out of shared logs and source control.

cURL

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

Python

import requests

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

Node.js

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://stripe.com',
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));

These examples show the basic request shape; add the documented cookie or authorization parameters for your target site. A login may also depend on CSRF state, a specific user agent, or other session conditions, so a cookie alone is not guaranteed to reproduce every browser session.

• Cookie banners, newsletter popups, and chat widgets are removed before the shot, and each cleanup step can be turned off.
• Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed; response headers report the page verdict and billing status.
• An MCP server gives AI agents tools for screenshots, page information, and PDF capture.
• 1,000 screenshots per month are free with no card; paid plans start at $5 for 3,000 screenshots.

Create a free ScreenshotNeo account to get 1,000 screenshots a month with no card.

6. Troubleshooting

Symptom	Likely cause	What to do
The captured page shows a sign-in screen	The browser session expired, the wrong profile is open, or the page requires another authentication step.	Sign in again in that browser profile, complete MFA if prompted, reload the target page, and capture the visible tab after confirming the protected content appears.
Part of the page is missing	The extension captures only what is visible in the viewport.	Scroll to the desired area for a viewport shot, or make a browser full-page screenshot and import it.
The editor does not open the expected image	The extension may not have been clicked on the intended tab, or the browser may have blocked its action.	Return to the authenticated target tab, verify the page is visible, click the extension again, and check the browser’s extension controls.
A full-page import is blank or incomplete	The source browser capture may not have completed, or the page may load content as you scroll.	Wait for the page to finish loading, scroll through lazy-loaded sections before capturing if needed, and inspect the saved image before importing.
Automated API capture shows an access-denied or challenge page	The site may reject automated traffic, or the supplied authentication state may be incomplete or expired.	Use credentials only where you have permission, refresh the session data securely, and check whether the site permits automated access. A cookie-injection API cannot guarantee bypass of a site’s access controls.

7. Performance, reliability, and cost

The extension route avoids building a capture pipeline: the page is already rendered in your browser, and you capture the visible screen. Its main limitation is coverage; scrolling pages require multiple captures or a separate full-page browser capture. The import workflow adds a save-and-import step but is appropriate for long pages.

An API is better suited to repeatable jobs, scripts, and agent workflows, but it introduces network requests and depends on the target site’s load behavior and authentication rules. Keep timeouts reasonable, handle unsuccessful HTTP responses, and do not assume every login cookie remains valid indefinitely.

Screenshot.rocks’ reviewed workflow is described as a free editor and extension with no account or watermark requirement. ScreenshotNeo’s stated plans are 1,000 shots per month free with no card; 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. Choose based on whether you need a manual mockup or recurring API captures, not on an assumption that one workflow replaces the other.

FAQ

Can I paste a session cookie into Screenshot.rocks?

The official workflow reviewed for this guide does not document manual cookie entry. Sign in in your browser and capture the active tab.

Does the Screenshot.rocks extension capture the whole page?

No. It captures the visible part of the active tab. Use a browser full-page screenshot and import it for a long page.

Can an API capture a page that requires login?

Some screenshot APIs accept cookies or authorization inputs. That is a separate product workflow; confirm the service’s current supported inputs and data-handling terms.

Is it safe to share a screenshot from a private page?

Only if you are authorized to share everything visible in it. Review the image for personal, account, and customer information before exporting or publishing.