Building Mobile, Steam, and Web Assets from a Single Source
Release the same game on mobile stores, Steam, and a web game portal at once, and the number of images you need balloons into the dozens almost immediately. Tall portrait screenshots, wide capsules, thumbnails the size of a fingernail, text-free background art — every one has a different shape and a different job. Redrawing each from scratch is a workload problem, but it's also a consistency problem: your hero's expression and your colors drift a little on every platform, and soon it stops looking like the same game.
The fix is to design a master that belongs to no platform before you produce anything for any of them. The composition of the key art itself is covered in Key Art Basics, so this post focuses on the working structure and order for splitting that art, plus your gameplay captures, into many outputs.
Separate the Master from Its Derivatives
Start by thinking of your files as two kinds. The master is an editable working file where background, characters, logo, and copy each remain live and separate. Derivatives are the exports you crop and flatten to fit a specific slot. Steam capsules, feature graphics, portal thumbnails, and store screenshots are all derivatives.
There's one rule: edit the master, then re-export the derivatives. The moment you start nudging a character around inside the capsule file itself, you have to repeat that same change by hand in every other derivative, and soon nobody knows which file is current.
Make the Master Larger Than Your Largest Output
Images shrink cleanly but blur when enlarged, so set your master resolution with generous headroom over the largest output you plan to make. Output sizes differ by platform and change over time, so before you start, check current references such as Steam capsule sizes or mobile screenshot sizes and use the largest value as your baseline.
Tips for giving an illustrated master a roomy canvas are in the key art post above. The same principle applies to gameplay captures and app screens, with one difference: unlike a painting, you can't paint more in later.
- Render resolution: Capture gameplay at the highest resolution the game can render, not at whatever your monitor or device happens to be.
- Wider framing: Pull the camera back a little and take one extra shot. Then the scene won't run out whether you crop it tall or wide.
- With and without UI: Save the same moment with the HUD on and with it off, and you've got your store screenshot source and your banner and thumbnail source in one pass.
- App screens: App UI blurs the instant you scale it up, so capture at native resolution on the largest device screen you have.
Split Layers by Role
A master flattened into a single image can't meet different platforms' different demands. One slot needs a logo, another needs text-free art, a third takes a different line of copy per language. Keep at least the following as separate layers or separate files.
| Layer | Why Keep It Separate | Where It's Mostly Used |
|---|---|---|
| Background art | Position and crop change the most with aspect ratio | Every derivative, text-free background slots |
| Hero / key object | Size and position need adjusting slot by slot | Capsules, thumbnails, banners |
| Game logo | Some slots take the logo on its own, and its placement differs per ratio | Capsules, library logo, portal thumbnails |
| Copy / captions | Swapped per language, and some slots are better off without any | Screenshot sets, social images |
| Effects / decoration | Often turn to clutter when shrunk and have to go | Large banners, press kit images |
| Seasonal / channel-specific elements | Short-lived elements like a launch celebration line | Derivatives for social and your own site |
Some slots, like the Steam library, take the background art and the logo as separate files and overlay them for you — so if you paint the logo into the background from the start, pulling it out later is far harder. Check each slot's requirements before you flatten anything.
Save Safe Areas as Guide Layers
You've probably already applied the principle of placing the hero where several crop frames overlap, back at the key art stage. To reuse one master across many derivatives, add two more things to that: the spots where other elements get layered on top of the image, and the spots where a platform covers or trims the edges.
| Type | What It Marks | Examples |
|---|---|---|
| Crop area | What survives when cut to each output ratio | Frames for a wide banner, a tall cover, a square thumbnail |
| Overlay area | Where elements such as logos and captions get added later | Background art that gets a separate logo overlaid, the top of a screenshot where a caption band goes |
| Obstruction area | Edges a platform or device screen may cover or trim | Icons clipped by rounded corners, spots where a platform overlays buttons or info |
Make one guide layer of each kind for each output and stack them at the top of the master file. Name the layers after the output ("Steam header", "portal thumbnail") and hide them on export. Set up this way, checking a new source is just a matter of switching the guides on one at a time.
Say a hypothetical space exploration game gets new art for a seasonal event. Turn on the guide set, confirm in one view that the ship lands inside every crop frame and that nothing essential sits under the logo and caption areas, and only then start on derivatives. If something's off, you can fix it in the master before a single derivative exists.
Produce Variations Starting with the Most Constrained Slot
With the master ready, it's time to export. Order the work by constraint: the most demanding slot first. A composition that passes the hard slots mostly works in the roomy ones too, and any problem shows up early, while fixing the master is still cheap.
- The smallest-displayed slot: Start with images that get shown shrunk down, like the small list capsule or a portal thumbnail. If the hero and logo don't read here, that's the signal to rework the master layout.
- Extreme aspect ratios: Next, fit the slots whose shape differs most from the master, such as a very wide banner or a tall cover. If the background runs short, this is when you extend the master.
- Text-free version: Make a pure-art version with the logo and copy removed. Text is easy to add later and hard to remove from a flattened image.
- Screenshot sets: Build the mobile store set and the Steam set from the same gameplay captures. Share the caption voice and color rules, and change only the layout to suit each orientation and viewing environment.
- Roomy slots: Large banners, high-resolution press kit images, and social images come last. By now you're just arranging already-proven elements across more space.
What Changes per Platform, and What Stays
Coming from one master doesn't mean every output has to look identical — people see them in different environments. Decide in advance what you'll adapt and what you'll keep fixed, and you won't have to re-think it for each derivative.
| Aspect | Mobile Stores | Steam | Web Portals |
|---|---|---|---|
| Viewing environment | Phone screen, swiped with a thumb | Monitor, in a list of capsules side by side | Browser grid, among dozens of thumbnails |
| Adjust | Larger captions, one message per image | Art and logo first, wide composition | Hero large, scene readable at a glance |
| Strip out | Quiet background detail | Explanatory copy | Small text and decorative effects |
What stays the same everywhere: the hero's look and expression, the signature colors, the logo, and the voice of the copy. The whole point of a single master is that a player who saw your character on Steam recognizes it instantly when they run into it again on a phone store.
At the screenshot-set stage, a tool like StoreShot — where you swap just the captions and images in one template, export every iOS and Android size at once, and use the PC/Steam category for Steam images too — makes it much easier to run one capture source across several platforms.
Wrapping Up
Capture generously, split layers by role, and save safe areas as guide layers — that's the preparation. Then export derivatives starting with the small slots and the extreme ratios, and the amount of backtracking drops sharply. One habit, fixing things in the master rather than the derivative, is what keeps the maintenance load from growing every time you add a platform.