Steam Store Page English Checklist for Non-Native Indie Devs
A section-by-section checklist for making your Steam store page read naturally in English, with before-and-after example lines and fixes for mistakes that non-native writers often make.
Your Steam page is often the first thing a player reads, and it may be the only thing. If the English sounds stiff or translated, some players will assume the game is the same. You don't need perfect literary English. You need clear, natural sentences that sound confident and match the tone of your game.
This checklist goes through the page in the order a visitor reads it. Each step tells you what to check and how to fix it. Every example line below was made up for this guide.
Before you start
- Copy all your page text into one document: short description, "About This Game", feature bullets, system requirements notes, and any text inside your capsule images or GIFs.
- Read it aloud. If you run out of breath or stumble over a sentence, it's too long or the word order is unnatural.
- Make a term list. Write down every game-specific word (your currency, classes, places, mechanics) and decide on one spelling and one capitalisation for each. Most of the fixes below depend on this list.
1. The short description
The short description sits next to your capsule art. It's the line people skim most.
- Start with what the player does, not with your studio's feelings. "A cozy farming game where you rebuild a flooded village" works better than "We are proud to present our first game."
- Use one or two sentences at most. Steamworks enforces a character limit, so watch the counter there.
- Cut "very", "really" and "unique". They take up space and don't tell the reader anything.
- Check articles (a / an / the). Missing articles are one of the most common things that make English sound translated.
Before: "Unique roguelike where player must survive in dark dungeon full of monsters." After: "A roguelike where you fight your way out of a dungeon that rebuilds itself every run."
The fix adds articles, changes "player" to "you", and swaps a vague word ("unique") for a concrete hook.
2. The "About This Game" section
- Lead with the fantasy or the hook in the first two lines. Many visitors stop reading after that.
- Keep paragraphs short, around two to four sentences each.
- Stick to one point of view. Pick "you" (second person) and keep it. Switching between "you", "the player" and "the hero" in the same section reads as a translation.
- Keep one tense. Story setup usually works best in present tense: "The kingdom falls. You wake up in the ruins." Drifting into past tense halfway through is a common problem.
- Don't translate idioms word for word. If a phrase is a saying in your language, rewrite the meaning in plain English instead.
Before: "In this game you will be able to explore the big open world and you can also craft many items and also you can fight with bosses." After: "Explore a hand-drawn open world, craft gear from what you scavenge, and take on bosses that learn from your tactics."
The fix turns three "you can" clauses into one list of active verbs and adds a specific detail to each item.
3. Feature bullets
- Start every bullet with a verb or a noun, and do it the same way each time. Don't mix "Explore...", "Crafting system..." and "You can trade..." in one list.
- Use parallel grammar. If one bullet ends with a full stop, all of them should.
- Back each claim with a concrete detail. "Many weapons" says less than "40 weapons, each with its own combo tree", as long as the number is true for your game.
- Check that capitalisation matches your term list. If it's "Soul Shards" in one bullet, it shouldn't be "soul shards" in the next.
Before:
- Big world to explore
- Crafting
- you can play coop with friends!!
After:
- Explore five biomes, each with its own weather and wildlife
- Craft weapons and traps from salvaged parts
- Play the whole campaign in two-player online co-op
4. False friends and translated vocabulary
False friends are words that look like a word in your language but mean something different in English. Check your page for these:
- "Actual" / "actually" often get used to mean "current" / "currently". In English, "actual" means "real".
- "Eventually" gets used to mean "possibly". In English it means "in the end".
- "Sensible" gets used to mean "sensitive". In English it means "reasonable".
- "Assist" gets used to mean "attend" or "watch". In English, "assist" means "help".
- "Realise" gets used to mean "create" or "make". In English it usually means "understand".
- "Possibility to" usually sounds better as "the option to", or just "you can".
- "Gameplay of 10 hours" sounds better as "about 10 hours of gameplay".
If you're unsure about a word, look it up in an English-only dictionary, not a bilingual one, and read the example sentences.
5. Tone and register
- Match the page to the game. A horror game page shouldn't read like a cheerful sales flyer, and a cozy game page shouldn't sound like a legal document.
- Avoid exclamation marks in a row. Use one at most, and use it rarely.
- Avoid formal phrases like "the aforementioned", "in order to" or "it is possible to". These often come from translation tools or school English.
- Use contractions ("you'll", "it's", "don't") in casual or friendly games. They make the text sound more natural.
6. Game terms and capitalisation
- Capitalise proper names (places, factions, named characters).
- Decide whether mechanics are capitalised. Either style is fine. What players notice is inconsistency.
- Don't capitalise ordinary nouns for emphasis ("Explore the World and fight Enemies"). In English this looks like a mistake.
- Make the page match the game. If the store page says "Mana" and the in-game UI says "MP", pick one, or explain the link the first time.
7. Small things players notice
- Use straight or curly quotes, but not both.
- Don't put a space before ! ? : ; in English. This is normal in French, so check carefully if French is your first language.
- Write numbers consistently: "2-4 players" or "two to four players", not both.
- Use one variety of English. US or UK spelling is fine ("color" / "colour"), but don't mix them.
- Check text inside images. Spell-checkers can't see it, and fixing it means re-exporting the image.
8. A quick self-test before you publish
Answer each of these with yes or no:
- Can a stranger explain what the game is after reading only the short description?
- Does every paragraph use the same point of view ("you")?
- Does every paragraph keep one tense?
- Are all feature bullets written in the same grammatical style?
- Is every game term spelled and capitalised the same way everywhere, including in images?
- Did you read the whole page aloud without stumbling?
- Did you remove "very", "unique", "many" and double exclamation marks?
- Did you check every word on the false-friends list?
If you answered "no" to any of these, fix that part before you go live or update your page for a festival.
Fill-in template for your short description
Copy this, fill in the brackets, then cut anything that doesn't earn its place:
"A [genre] where you [main action] to [goal], [one unusual twist]."
Examples of the shape (all made up):
- "A puzzle platformer where you rewind time to save a lighthouse keeper, one tide at a time."
- "A tactics game where you lead a travelling circus through a war, and every act is a battle."
A note on tools
Grammar checkers and AI tools can catch typos and missing articles. They don't know your characters or your term list, and they won't notice that a joke landed wrong. Use them for a first pass. Then read the result aloud yourself, or ask a native English-speaking player you trust to read the page before launch.
Custom large-print crossword packs for senior living activity directors ยท $12.99
Get it on Gumroad