CS2 Screenshot API

Your first screenshot

Start with your SteamWebAPI key and a full CS2 inspect link. Send the key in the X-Api-Key header and URL-encode the link. No styling options are needed for the default image shown above.

curl --get 'https://www.steamwebapi.com/steam/api/screenshot' \
  --header 'X-Api-Key: YOUR_STEAMWEBAPI_KEY' \
  --header 'Idempotency-Key: YOUR_UNIQUE_REQUEST_ID' \
  --data-urlencode 'url=YOUR_FULL_INSPECT_LINK' \
  --max-time 100 \
  --dump-header screenshot-headers.txt \
  --output screenshot-response

Replace the three placeholders before running the request. Check the saved headers: 200 with image/avif means you can save the body as screenshot.avif. A 202 body is JSON containing a pending job.

Request a transparent cutout

Insert these options before --max-time in the request above and choose a new Idempotency-Key. Use mode=back for the reverse side.

--data-urlencode 'mode=front' \
--data-urlencode 'view=transparent' \
--data-urlencode 'width=1920'

Parameters and defaults

Send these options as query parameters to /steam/api/screenshot. The Key header and key query parameter are also accepted for authentication.

Scroll the table sideways to see all options.

Use both, not bothsides. Custom background-image URLs, alignment settings, logos and watermarks are not public options on this endpoint. Unsupported or repeated parameters return 422.

Handle the image or a pending job

Always inspect the HTTP status before treating the response as an image. A successful request can return the result immediately or provide a job ID while rendering finishes.

200 · screen

AVIF bytes with Content-Type: image/avif, displayed inline.

200 · download

The same AVIF, with an attachment filename of screenshot.avif.

200 · base64

JSON with status: "success" and image: "data:image/avif;base64,...".

202 · pending

JSON with a job ID and a Retry-After header. Wait for that delay before requesting the result.

{
  "status": "pending",
  "job_id": "YOUR_JOB_ID",
  "idempotency_key": "YOUR_UNIQUE_REQUEST_ID"
}

Retrieve the result

Use the same API key and the returned job_id. Leave out the inspect link and render options. If the job is still running, the response is 202 again.

curl --get 'https://www.steamwebapi.com/steam/api/screenshot' \
  --header 'X-Api-Key: YOUR_STEAMWEBAPI_KEY' \
  --data-urlencode 'job_id=YOUR_JOB_ID' \
  --data-urlencode 'format=download' \
  --max-time 100 \
  --dump-header screenshot-headers.txt \
  --output screenshot-response

Save the completed image. Results expire after three hours. Store the image yourself for longer use; the API does not return a public image URL.

Retry without creating another render

Choose a unique Idempotency-Key before the first request. After a timeout, reuse that key with the same inspect link and options. A new image configuration needs a new key. Result lookups and retries still count towards your screenshot quota.

For 422, check the parameter combination. For 429, wait for Retry-After. A 410 means the stored image expired. See the full reference for all error codes and retry rules.

From inventory data to a visual listing

Use the Steam Inventory API to find the CS2 item, then pass its available inspectlink into the screenshot endpoint as url. Items without an inspect link should be skipped.

1. Request the image on your server. Keep your SteamWebAPI key out of public HTML and browser requests.
2. Save the successful AVIF response. Use your own storage or CDN to serve it alongside the listing.
3. Reuse the saved image. Serve that file when visitors open the item, rather than starting a new render for every page view.

For a marketplace listing, both sides show the item in one image. For inventory grids, a transparent front view can sit directly on your own background. Use a separate back view when visitors need a closer comparison.

Need visitors to rotate an item instead of viewing a still image? Explore the CS2 3D Viewer.

Your key, with separate screenshot limits

Authenticate with your existing SteamWebAPI key. Screenshots are included at no extra cost in every package, including Free and Free+, subject to your package limits. Screenshot-specific limits take precedence; when none are configured, your package's Global limits apply. Explicit zero day/month quotas block access. First use may take longer while access is initialized.

Screenshot requests have their own per-minute, per-day and per-month limits. They do not consume ordinary SteamWebAPI API credits. Read your current limits and counters on demand:

curl 'https://www.steamwebapi.com/steam/api/screenshot/usage' \
  --header 'X-Api-Key: YOUR_STEAMWEBAPI_KEY'

{
  "status": "success",
  "active": true,
  "limits": { "minute": 100, "day": 1000, "month": 10000 },
  "usage": { "minute": 1, "day": 25, "month": 240,
             "total": 500, "blocked": 0 },
  "timezone": "UTC",
  "period": "calendar",
  "unit": "authenticated_requests"
}

Illustrative numbers, not a plan allowance. A null limit means unlimited. Day and month counters reset at UTC calendar boundaries. total covers retained history, not necessarily lifetime usage. Avoid checking usage before every render.

Frequently asked questions