SteamCall Images

Game item images.
Ready for your
interface.

Bring Team Fortress 2 items into focus. SteamCall Images prepares WebP and AVIF variants for inventory lists, trading views and item details.

Get started with Images Explore the images

See real TF2 items previously prepared with SteamCall Images.

The Rocket Jumper from Team Fortress 2 — TEAM FORTRESS 2Prepared Images output

Mann Co. Supply Crate Key from Team Fortress 2 — TEAM FORTRESS 2Prepared Images output

WebP & AVIF

64 / 128 / 256 / 512

Shared preparation

Controlled delivery

Made for your interface

One image.
Every place you need it.

Explore prepared TF2 item images across four size bounds and two formats. Choose the file that fits each place in your interface.

Explore prepared variantsPreviously prepared TF2 item images

THE ROCKET JUMPER / TF2Loading image

256 × 256 pxWEBP · 8.0 KB

TF2 item

Size bound px

64128256512

Format

WebPAVIF

Each choice loads a previously prepared SteamCall Images file. The bound limits its dimensions; the original proportions are preserved without upscaling.

Loading image

The image area is reserved while the browser loads this file.

Three TF2 items · four size bounds · two formatsVariant docs

ONE SET OF VARIANTS

Inventory rowsTrading interfacesItem detail views

Fits the way you build

Your inventory.
Images included.

Add include=images to Live Inventory or Current. Ready delivery URLs can arrive alongside item descriptions; pending variants require later polling.

Keep the API Credential on your server. Your frontend receives the returned image URLs, not your key.

Inventory integration guide

Images access and an active Service Account binding are required. Current also needs an existing Inventory revision.

GET /v2/steam/users/{steam_id}/inventory/440/2/current?include=images&images=128&image_formats=avif
X-API-Key: <SERVER_SIDE_CREDENTIAL>

// descriptions[].steamcall.images — shortened TF2 excerpt
{
  "status": "ready",
  "resource": {
    "variants": [{
      "size": 128, "format": "avif", "status": "ready",
      "width": 128, "height": 128,
      "url": "RETURNED_AVIF_URL"
    }]
  }
}

POST /v2/images/resolve
X-API-Key: <SERVER_SIDE_CREDENTIAL>
Content-Type: application/json
Idempotency-Key: <YOUR_OPERATION_KEY>

{
  "selector": {
    "type": "image_id",
    "image_id": "<YOUR_KNOWN_IMAGE_ID>"
  },
  "sizes": [128, 256],
  "formats": ["webp", "avif"]
}

// Inspect status, variants and settled — not only HTTP 200.

<!-- Example: The Rocket Jumper, 128 px prepared variant. -->
<picture>
  <source type="image/avif" srcset="RETURNED_AVIF_URL" />
  <img
    src="RETURNED_WEBP_URL"
    width="128"
    height="128"
    alt="The Rocket Jumper from Team Fortress 2"
    loading="lazy"
  />
</picture>

<!-- Never send the API Credential to the browser.
     Handle load errors with a local fallback. -->

Shortened TF2 response shape. Private IDs and delivery URLs are replaced with placeholders.

Not using Inventory? Start with Images.

Resolve, Batch and Poll are independent of Current.

Resolve

Select a known image or an approved source.

Resolve & poll

Follow readiness

Poll the returned status URL. Keep partial results.

States & errors

Work in batches

Submit up to 100 selections with independent outcomes.

Batch preparation

Batch size is a request limit, not a throughput guarantee.

Less infrastructure. More interface.

Prepared once.
Delivered with control.

Shared media preparation behind the scenes.
Workload-specific access where it matters.

Supported sourceSteam item image
Shared preparationPrepared for reuse
Ready variantsWebP + AVIF
Your applicationControlled delivery

Share prepared media safely.

SteamCall can reuse a prepared image for the same supported source. Your application receives URLs under its own access rules, and API responses remain private.

Keep delivery tied to your workload.

Delivery URLs belong to a Service Account binding in a Project. Saved URLs preserve media identity, but access can be revoked.

Binding lifecycle

Supported item images can be prepared ahead of your request. New images may still need time before their variants are ready.

Product access

One product.
Clear access boundaries.

Images is a separate SteamCall product. An API Credential alone does not grant image delivery access.

Verify Images access in Billing before setup.

Read the setup requirements

01
Images access in Billing
Verify product access for your account.
02
Project → Service Account
Choose the workload and its Images scopes.
03
Active delivery binding
Create the current binding for that Service Account.

How delivery is measured

Data transferredMeasured in GB

Delivery requestsMeasured as operations

These are measurement units, not your account totals. View actual usage and its reporting period in Billing. Preparing an image is not delivering it.

Images delivered across SteamCall

Global delivery statistics are not available yet. Totals will appear once reporting covers the full period.

Delivery requests are not unique images or confirmed views. Your account usage is available in Billing.

Before you build

A few good
questions.

The contract, without the guesswork.

Explore the documentation

Which item images are supported?

These examples show Team Fortress 2 items. SteamCall Images prepares images from supported Steam sources; it does not accept arbitrary uploads or image URLs. See the source guide for the current scope.

Read source rules

Will every image be ready on the first request?

No. Preparation runs asynchronously. An image may already be prepared when you request it, but a new image can still be processing or partial. Keep ready variants, show a fallback where needed, and poll the returned status URL within a bounded deadline.

Understand readiness

Do I need to use Inventory?

No. Resolve, Batch and Poll work independently of Current. Inventory enrichment is a convenient path when you already read inventories. Current still requires an existing Inventory revision; preparing an image does not create one.

Explore Inventory enrichment

Are delivery URLs public forever?

No. A ready URL identifies immutable media in a Service Account binding namespace. Credential rotation preserves it, but binding changes, workload status and product access can affect delivery. Use returned URLs exactly as supplied and never append an API Credential.

Read about URL lifetime

How do access and usage work?

Images has separate product access. Delivery operations and transferred bytes, displayed in GB, are observed in Billing. These meters do not debit prepaid credit or trigger automatic overage. Resolve, Batch and Poll do not consume delivery meters; API request limits still apply. Preparation is not delivery.

Understand delivery usage

How do I get started?

Start by checking Images product access in Billing, choosing a Project and Service Account, and creating its current delivery binding. A Credential or binding alone does not grant access.

Read the setup requirements

Build with SteamCall Images

Build the interface.
Not the image pipeline.

Choose your Project and Service Account, then set up image delivery.

Get started with Images Explore the API

Images access and an active binding are required.

Game item images.Ready for your interface.

One image.Every place you need it.

Your inventory.Images included.