Steam screenshots: 1920x1080, five minimum, gameplay only

Steam asks for at least five 16:9 screenshots, 1920x1080 or larger, showing gameplay. A generated image is not gameplay, so capture real frames instead.

4 min readSume
All posts

No: an AI-generated image should not be one of your Steam screenshots. The Steamworks page asks for at least five screenshots at 1920x1080 or larger in 16:9, and says they must show gameplay. Use generated images for capsules and key art, and capture the screenshots from the running game.

Steam rules are from the Steamworks store-assets page and size limits from Sume's image docs, both read 2026-10-01. The Steam page carries no last-updated date.

What does Steam require for screenshots?

Four items on the page, summarized here.

Steam screenshot requirements, read 2026-10-01.
RequirementValue on the page
Minimum size1920x1080
Aspect ratio16:9
CountMinimum 5
ContentMust show gameplay

Where can a generated image still help?

Capsules, the page background and promotional art are graphic assets, not gameplay captures; the same Steam page lists their sizes. See Steam capsule sizes for those, and the bundle header post for the one that exceeds 3:1.

Can Sume produce a 1920x1080 image if I need one?

For a 16:9 graphic, aspect_ratio: "16:9" is in the documented list. For exact pixels with ChatGPT Image 2.5 the docs say custom image_size needs "both edges must be multiples of 16": 1920 is (120 x 16), but 1080 is not (67.5 x 16), so 1920x1080 is not a valid custom size. 1920x1088 is, and so is 2048x1152.

The docs also cap custom sizes at a 3840 maximum edge, aspect ratio at most 3:1, and 655,360–8,294,400 pixels. None of this changes the Steam rule: a bigger or sharper generated frame is still not gameplay.

What should I do instead?

Capture at least five real frames at 1920x1080 or higher in 16:9, covering different moments of play. Keep the generated work for the assets Steam treats as art, and check the Steamworks page again before submitting, since it is undated.

Sources

Related posts

More in Use cases

All Use cases posts

Written by Sume