Workspaces

A workspace is a separate area inside your account, for example one per project or one per client. Each workspace has its own API keys, custom storage, webhook and logs, so the projects do not mix. Plan, credits, billing, the team and rate limits stay on the account. Owners and admins manage workspaces on the Workspaces page of the dashboard, which opens from the workspace switcher at the top of the sidebar. This page is part of the documentation.

What belongs to a workspace

Every account starts with one workspace named Default. Everything you created before workspaces existed is in it.

The API key selects the workspace

The API key selects the workspace. There is no new API parameter and no new header: a request made with a key of workspace B uses the storage, webhook, logs and cache of workspace B. A signed URL works the same way, through its public key, and the signing secret must be in the same workspace as the public key.

The switcher in the dashboard sidebar chooses which workspace the dashboard pages show. API keys you create there belong to the workspace that is selected.

Plan limits

The Workspaces page shows how many workspaces you have and how many your plan allows. If you downgrade to the Free plan with more than 10 workspaces, existing workspaces keep working, with all their keys. You cannot create a new workspace until the account is below the limit.

Each workspace has its own cache

This also applies to the cache management endpoints: a purge or a delete only affects renders of the key's workspace.

Monthly credit cap

All workspaces use the account's credits. An owner or admin can give a workspace an optional monthly credit cap on its edit page, for example 500 credits for a client project. Leave the field blank for no cap.

• The cap counts the credits the workspace used in the current billing period. It resets with the account's credits: on the first day of each month on the Free plan, and when each invoice is paid on a paid plan.
• A request needs room in both: the account must have credits left, and the workspace must be under its cap. When the account is out of credits, you get insufficient_credits first.
• When the cap is reached, the API answers 403 with the code workspace_credit_cap_reached. The body has the same shape as other authorization errors. A batch is refused before it starts when it needs more credits than the cap has left.
• Cache hits use no credits, but like insufficient_credits, the cap error is also returned for them once the cap is reached.

{
  "error": {
    "type": "authorization_error",
    "code": "workspace_credit_cap_reached",
    "message": "This workspace has used its monthly credit cap of 500. Raise the cap in the dashboard or wait for the next billing period.",
    "retryable": false,
    "docs": "https://renderscreenshot.com/docs/errors/error-codes"
  },
  "request_id": "5f0c1b9e-2d47-4a8e-9b61-3e7a0c4d8f12"
}

The Usage page shows the account's credits and a table of the credits each workspace used this period.

Team access

Owners and admins see every workspace. A member sees only the workspaces they are added to. To change access, open a workspace's edit page and check or uncheck its members under Member access.

When you invite someone as a member on the Team page, choose the workspaces they can open. With none chosen, the invitation adds them to the Default workspace. Owners and admins always have access to all workspaces.

Move API keys

An owner or admin can move an active API key to another workspace of the same account. The raw key does not change, so the code that sends it keeps working. There are three places to do this:

• API Keys page: select Move next to a key, choose the target workspace and confirm.
• Workspaces page: select Move keys next to a workspace, check the keys, choose the target workspace and confirm.
• Delete a workspace: choose Move its active API keys to a workspace before you delete it (see below).

From the next request, a moved key uses the new workspace's storage, webhook, CDN domain, credit cap and cache. An async screenshot that is already in the queue also goes to the new workspace. A batch that is already running keeps its old workspace.

• Old request logs and batches stay in the old workspace, so the usage of each workspace stays correct.
• A signing key pair moves as one unit: moving the public key or the secret key moves both, so signed URLs keep working.
• A signing key created before pairs were linked cannot move, because its signed URLs would stop working. Create a new signing pair in the target workspace instead, then revoke the old keys.
• A revoked key cannot move.

Delete a workspace

Deleting a workspace permanently deletes all its data: its request logs, batches, storage configuration and CDN domain, and its API keys unless you move them (requests made with a deleted key then fail with 401). The credits it already used still count for the account, so usage totals for billing do not change.

1. Open the workspace's edit page.
2. Under Danger Zone, choose what happens to its API keys: Revoke and delete its API keys, or Move its active API keys to another workspace.
3. Type the workspace name exactly.
4. Select Delete workspace.

The move and the delete happen together: if the delete fails, no key moves. Old unlinked signing keys cannot move, so they are deleted in both cases; the form lists them before you confirm.

A CDN domain must be revoked before its workspace can be deleted. The default workspace cannot be deleted; it is removed only together with the account.

Last verified 2026-10-28 against the workspace, API key, cache, credit and dashboard code.