What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Yes, you can use multiple API keys for a screenshot API—but treat them as separate credentials, not as extra capacity. Create one clearly named key for each environment, application, or trust boundary; keep keys in server-side secrets; select the right key in one configuration layer; and rotate a replacement before revoking the old key. This isolates staging from production, limits the blast radius of a leak, and lets you attribute usage. It does not guarantee higher rate limits or a larger monthly quota.
What multiple keys are actually good for
A key is an identity and credential. Multiple identities help you separate workloads even when they share one provider account.
- Environment isolation: use separate staging and production credentials so a staging leak does not expose production access.
- Application isolation: give a dashboard, reporting worker, and customer-facing API different keys so usage and failures are attributable.
- Operational roles: where a provider supports roles, keep server-side signing credentials separate from public verification or live-capture credentials.
- Safer rotation: replace one credential without editing every workload that uses another.
- Incident containment: revoke only the compromised or unused key instead of taking every integration offline.
Do not assume that adding keys bypasses throttling. A provider can enforce limits per key, account, plan, IP address, or a combination. Only the provider’s current plan and limit documentation can establish how capacity is measured.
Design a key layout before creating credentials
Use names that identify ownership and purpose
Names should answer “where is this used?” without containing the secret itself. Examples include production-web-capture, staging-preview-worker, and billing-pdf-job. Add an owner or rotation date if your secret manager supports metadata.
#1 Best Overall
- POWERFUL SECURITY KEY: The Security Key C NFC is the essential physical passkey for protecting your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with Google, Microsoft, and Apple. A single Security Key C NFC secures 100 of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your Security Key C NFC via USB-C and tap it, or tap it against your phone (NFC) to authenticate. No batteries, no internet connection, and no extra fees required.
- TRUSTED PASSKEY TECHNOLOGY: Uses the latest passkey standards (FIDO2/WebAuthn & FIDO U2F) but does not support One-Time Passwords. For complex needs, check out the YubiKey 5 Series.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
Choose a trust boundary
Create a new key when code runs in a different environment, team, account, or deployment pipeline. A single key shared by local development, CI, staging, and production makes auditing and revocation unnecessarily disruptive.
Separate key roles when the provider offers them
RenderScreenshot documents live keys for API access, public keys for signed-URL verification, and secret keys for server-side signed-URL generation. Its dashboard flow is to create a key, choose its type, name it, and copy it immediately; the documentation says the value is shown only once. Store it at creation time, rotate periodically, and revoke unused keys.
Provider authentication differs
| Provider | Authentication behavior | Multiple-key implication |
|---|---|---|
| RenderScreenshot | Live, public, and secret key roles are documented. | Use a role appropriate to the operation; save the value immediately because it is displayed once. |
| Screenshotbase | The free plan allows one API key; paid plans allow multiple. It supports an apikey header and warns that query-string keys may appear in access logs. |
Check the plan before designing separate credentials and prefer the header. |
| ScreenshotEngine | POST /v1/screenshot uses a Bearer token in Authorization; its GET endpoint requires an api_key query parameter. |
Keep calls on your backend, never in browser code or public URLs; replace and revoke an exposed key. |
| Screenshot Studio | The public API is unauthenticated and applies limits per IP. | There is no API key to create or rotate; protect capacity with IP-aware throttling. |
These are provider-specific examples, not a universal standard. Before implementation, confirm the current endpoint, header name, key roles, and plan rules for the service you selected.
Store and select keys on the server
Put each value in environment variables or a deployment secret manager. Never commit keys, embed them in React or other browser bundles, put them in shareable image URLs, or print them in request logs.
SCREENSHOT_API_KEY_PRODUCTION=replace-with-production-secret
SCREENSHOT_API_KEY_STAGING=replace-with-staging-secretCentralize selection so application code cannot accidentally use a production key in staging:
Rank #2
- POWERFUL SECURITY KEY: The YubiKey 5C NFC is the most versatile physical passkey, protecting your digital life from phishing attacks. It ensures only you can access your accounts
- WORKS WITH 1000+ ACCOUNTS: Compatible with popular accounts like Google, Microsoft, and Apple. A single YubiKey 5C NFC secures 100+ of your favorite accounts, including email, password managers, and more
- FAST & CONVENIENT LOGIN: Plug in your YubiKey 5C NFC via USB and tap it, or tap it against your phone (NFC), to authenticate. No batteries, no internet connection, and no extra fees required
- MOST SECURE PASSKEY: Supports FIDO2/WebAuthn, FIDO U2F, Yubico OTP, OATH-TOTP/HOTP, Smart card (PIV), and OpenPGP. That means it’s versatile, working almost anywhere you need it
- PRIMARY & SPARE KEYS: Just like having a spare house key, we recommend buying two YubiKeys - one for daily use and one as a spare. That way you’ll never get locked out of your accounts
function screenshotKey(environment) {
const names = {
production: 'SCREENSHOT_API_KEY_PRODUCTION',
staging: 'SCREENSHOT_API_KEY_STAGING'
};
const name = names[environment];
if (!name || !process.env[name]) throw new Error(`Missing screenshot key: ${name}`);
return process.env[name];
}
const key = screenshotKey(process.env.APP_ENV || 'staging');
// Pass key through the provider's documented header or parameter.
Fail closed when the expected variable is absent. Do not silently fall back to another environment’s credential.
Calling a provider with the selected key
Header-based authentication
For a provider that documents an apikey header, send the selected value server-side:
const response = await fetch('https://provider.example/v1/screenshot', {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'apikey': process.env.SCREENSHOT_API_KEY_PRODUCTION
},
body: JSON.stringify({ url: 'https://example.com' })
});
if (!response.ok) throw new Error(`Screenshot failed: ${response.status}`);Replace the host, path, payload, and header with the provider’s current documentation; the example domain is illustrative, not a service endpoint.
Bearer authentication
const response = await fetch('PROVIDER_POST_ENDPOINT', {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'Authorization': `Bearer ${process.env.SCREENSHOT_API_KEY_PRODUCTION}`
},
body: JSON.stringify({ url: 'https://example.com' })
});ScreenshotEngine documents this pattern for its POST endpoint. Its GET endpoint instead requires an api_key query parameter, which increases the risk of exposure through logs and history; use the POST route when it meets your needs.
Rotate a key without downtime
- Create the replacement. Name it for the same environment and workload, and record its creation and owner metadata.
- Add it as a second secret. Keep the old value available temporarily; do not overwrite the only deployed value before testing.
- Deploy configuration that can use the new key. A feature flag or dual-key configuration lets you switch instances gradually.
- Verify real requests. Check authentication, expected image or PDF output, timeout behavior, and provider response headers.
- Switch all instances. Confirm old and new deployments are not serving mixed configuration longer than necessary.
- Revoke the old key. Do this only after traffic and logs show that no workload still needs it.
- Remove the old secret. Delete it from deployment configuration, CI variables, local files, and backups subject to your retention policy.
For a suspected leak, shorten the overlap: create the replacement, deploy it immediately, revoke the exposed key, and review access logs. Do not wait for a routine rotation window.
Rank #3
- POWERFUL SECURITY KEY: The YubiKey 5 NFC is the most versatile physical passkey, protecting your digital life from phishing attacks. It ensures only you can access your accounts
- WORKS WITH 1000+ ACCOUNTS: Compatible with popular accounts like Google, Microsoft, and Apple. A single YubiKey 5 NFC secures 100+ of your favorite accounts, including email, password managers, and more
- FAST & CONVENIENT LOGIN: Plug in your YubiKey 5 NFC via USB and tap it, or tap it against your phone (NFC), to authenticate. No batteries, no internet connection, and no extra fees required
- MOST SECURE PASSKEY: Supports FIDO2/WebAuthn, FIDO U2F, Yubico OTP, OATH-TOTP/HOTP, Smart card (PIV), and OpenPGP. That means it’s versatile, working almost anywhere you need it
- PRIMARY & SPARE KEYS: Just like having a spare house key, we recommend buying two YubiKeys - one for daily use and one as a spare. That way you’ll never get locked out of your accounts
Multiple keys do not automatically raise limits
Separate credentials improve accounting and isolation, but cycling keys to evade a 429 response can violate provider terms and still fail if enforcement is account-wide or IP-based. Screenshot API documentation gives an example free plan of 60 requests per minute and 500 screenshots per month, with headers such as X-RateLimit-Remaining and X-Quota-Remaining; those figures are plan examples that may change. Screenshot Studio documents a 20-requests-per-minute limit per IP and does not require a key. Verify the current plan before relying on either number.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsHandle failures by type
- 401 Unauthorized: the key is missing, malformed, invalid, or revoked. Check the selected environment, header spelling, and secret deployment.
- 403 Forbidden: the credential may lack the required role, endpoint access, or account permission. Confirm plan and key scope.
- 429 Too Many Requests: you are throttled. Honor retry and reset headers, use exponential backoff with jitter, and reduce concurrency; do not switch keys merely to continue.
- Quota or billing error: the plan allowance is exhausted. Wait for the documented reset, purchase capacity, or reduce demand.
Reliability and cost controls
Use bounded retries
Retry only transient network failures and documented 5xx responses. Apply an increasing delay with jitter and a maximum attempt count. Do not retry authentication errors; fix configuration instead. Make jobs idempotent so a retry does not create duplicate downstream records.
Watch the right metrics
- Requests and successful captures by key, environment, and endpoint.
- Latency, timeout, 4xx, 5xx, and
429rates. - Remaining rate-limit and quota headers, where supplied.
- Estimated cost by workload and the date of the provider’s quota reset.
Redact Authorization, apikey, and api_key values before logs reach a central system. Log a key identifier or secret-manager reference instead.
Control concurrency
A queue with a provider-specific concurrency limit is safer than allowing every web request to launch a browser capture. Add timeouts, cancellation, and a dead-letter path for jobs that repeatedly fail. Cache identical captures only when the page’s freshness requirements allow it.
Or skip the browser setup
ScreenshotNeo provides a single HTTP endpoint and an MCP server for developers and AI agents. It accepts consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be disabled. Only clean shots are billed: bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Use a separate ScreenshotNeo access key per environment in your own secret manager, then call the API from your backend. Full parameter details are in the ScreenshotNeo API documentation.
Rank #4
- POWERFUL SECURITY KEY: The Security Key NFC is the essential physical passkey for protecting your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with Google, Microsoft, and Apple. A single Security Key NFC secures 100 of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your Security Key NFC via USB-A and tap it, or tap it against your phone (NFC) to authenticate. No batteries, no internet connection, and no extra fees required.
- TRUSTED PASSKEY TECHNOLOGY: Uses the latest passkey standards (FIDO2/WebAuthn & FIDO U2F) but does not support One-Time Passwords. For complex needs, check out the YubiKey 5 Series.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
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()
open("shot.webp", "wb").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(`ScreenshotNeo failed: ${res.status}`);
ScreenshotNeo also supports full-page captures with lazy images loaded, CSS-selector element capture, dark mode, 12 device presets or custom viewports, retina scale, PDF paper and page options, HTML/CSS input, custom JavaScript and CSS, pre-capture clicks, selector hiding, selector/delay/network-idle waits, request and resource blocking, custom headers, cookies, user agents, Authorization, timezone and geolocation, transparent backgrounds, resizing, selectable cache TTLs, signed image links, asynchronous jobs with signed webhooks, up to 100 URLs per bulk call, a usage API, and an OpenAPI specification. Its parameter names are compatible with those used by other screenshot APIs, easing migration.
An MCP server exposes take_screenshot, get_page_info, and capture_pdf to Claude, Cursor, and other MCP clients. Plans include 1,000 screenshots per month free with no card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account to get an access key.
Troubleshooting checklist
“It works locally but returns 401 in production”
Confirm the production secret is attached to every running instance, that the deployment was restarted after the secret changed, and that the code selects the production variable rather than a local default. Print only the variable name or a redacted fingerprint while diagnosing.
Recommended Free Tools
“Rotation broke some workers”
Some workers likely retained the old configuration or a stale secret-manager version. Roll out the replacement consistently, wait for readiness checks, then revoke the old key only after all workers report the new key identifier.
“A second key did not increase throughput”
The provider may enforce account, plan, IP, or global concurrency limits. Read the response’s rate-limit headers and plan documentation, then add queueing and backoff instead of cycling credentials.
Best Value
- Security Key : Protect your online accounts against unauthorized access by using FIDO2 and U2F authentication with T110. It's the world's most protective security key that works with windows, Mac OS, Linux as well as Chrome, Firefox, Edge and many other major browsers.
- Certified with the new FIDO2 standard, T110 provides the benefit of fast login and strong protection against phishing, account takeover as well as many other online attactks.
- Works with : Bank of America, Github, Google, Microsoft, DUO, Twitter, Facebook, Dropbox, Apple, ebay, BINANCE, mor and more.
- Fits USB-A port : Insert the T110 security key into the USB-A port of each service and log in conveniently with one touch
- For the driver download and user guide, please visit TrustKey Solutions Home support page.
“The key appeared in logs”
Remove query-string authentication where a header is available, add redaction rules for all credential fields, invalidate the exposed key, and inspect access logs for unauthorized use. ScreenshotEngine specifically advises backend calls and replacing and revoking an exposed key.
“The service has no key-management screen”
Some APIs, including Screenshot Studio’s public API, are unauthenticated. You cannot rotate a nonexistent credential; enforce your own IP, queue, and application-level controls and monitor the provider’s limits.
Key-management checklist
- One named key per environment or trust boundary.
- Secrets stored only in a manager or environment configuration.
- Header authentication preferred over query parameters.
- Centralized, fail-closed key selection.
- Redaction for every credential field and URL.
- Replacement tested before revocation.
- Routine and incident-driven rotation schedules.
- Quota, rate-limit, latency, and error monitoring.
- Backoff and queueing instead of key cycling.
Frequently Asked Questions
Should I use one key per customer?
Only when the provider supports that model and the operational value justifies the additional secret lifecycle. For most applications, one key per environment or workload is easier to secure and audit.
Can a browser application call a screenshot API directly?
Avoid it when the API uses a private credential. Browser bundles and network tools expose embedded keys; call the provider from your backend and return the resulting image or PDF.
How long should old and new keys overlap during rotation?
Keep the overlap only for the time required to deploy and verify every consumer. Revoke promptly after all instances use the replacement, and immediately after a suspected exposure.
What should I record for each key?
Record a non-secret name, environment, owner, creation date, intended endpoints or role, rotation date, and revocation status in your secret-management or inventory system.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
