A Game Release Checklist for a Small Indie Studio
Launch week is when small studios find out what they forgot. The build is done, the trailer is live, and then someone notices the store page still lists the wrong minimum specs, or the save file breaks on a clean install.

Launch week is when small studios find out what they forgot. The build is done, the trailer is live, and then someone notices the store page still lists the wrong minimum specs, or the save file breaks on a clean install. A game release checklist turns those surprises into boring line items you tick off weeks earlier.
This is the checklist we use at Fox Studios for our own releases, cut down to what a team of two to five people can realistically handle. It is split into time blocks counting back from launch day.
Why a game release checklist matters for a small team
Large studios have release managers, QA departments and a producer whose only job is to chase loose ends. Small teams have the same number of loose ends and nobody assigned to them. On our second release, we missed a localization string that crashed the game in German. It took four hours to patch, and the first 30 reviews in that region were angry.
A written list fixes that because it does not depend on memory. Ours lives on the same board as our tasks, which we described in our post about keeping a kanban board current, and every item has one owner and a due date. If something has no owner, it does not get done.
Eight weeks out: the store and the plan
- Lock the release date. Pick a Tuesday through Thursday and avoid the week of a major sale or a huge release in your genre.
- Finish the store page. Capsule art at every required size, at least five screenshots, a short description under 300 characters, and accurate tags.
- Set your price. We wrote a full guide on how to price your indie game on Steam without guessing. Decide your launch discount now, usually 10 to 20 percent.
- Plan the build pipeline. Know exactly who uploads builds, which branch is live and how a hotfix gets pushed.
- Agree on money. If more than one person is involved, the revenue split should be signed before launch, not after. Our post on revenue split agreements for a small indie game team covers what to write down.
Four weeks out: test like a stranger
This is the block most teams rush, and it causes most launch-day problems.
- Clean install test. Install the game on a machine that has never run it. Delete config folders first. You will be surprised what breaks.
- Minimum spec test. Run it on the weakest hardware you list on the store page. If it drops below 30 frames per second, change the listed specs or optimize.
- Save and load stress test. Save, quit, reload, repeat 20 times across different points in the game. Corrupted saves cause more refund requests than almost anything else.
- Controller and input test. Test keyboard, at least two controller types, and rebinding if you offer it.
- Language pass. Every language you support should be loaded and played through the first 15 minutes.
- Outside playtest. Give the build to three to five people who have never seen it. Watch, do not explain.
Log every bug with a severity: crash, blocker, annoying, cosmetic. Fix every crash and blocker. Be honest about the rest.
Two weeks out: press, creators and community
- Send keys to creators and press with a clear embargo date and time, including the time zone.
- Prepare a press kit folder: logo, screenshots, trailer file, a 150 word fact sheet and team contact.
- Write the launch announcement for your store page, social accounts and Discord ahead of time.
- Schedule a short launch day stream if anyone on the team enjoys it. If nobody does, skip it.
- Draft responses for the questions you know are coming: Steam Deck support, controller support, future updates, price.
Launch day and the first 72 hours
On launch day, someone should be at a desk for the full day with the build tools open. Not playing, not streaming, just watching for problems.
- Press the release button at least one hour before your announced time, then confirm the store page and download work from a separate account.
- Check crash reports and reviews every two hours for the first day.
- Have a hotfix branch ready. Our rule is that a crash affecting more than 2 percent of players gets a patch within 24 hours.
- Reply to negative reviews only with facts and fixes. We go deeper on this in how to handle negative feedback on your indie game.
- Post a short thank you update at the 72 hour mark with what you fixed and what is next.
The checklist advice we stopped following
A lot of launch guides say to cram in a final round of content right before release: one more level, one more boss, extra polish on the menus. The logic is that more content means better reviews. We tried this once and regretted it.
Every feature added in the last three weeks is a feature that skipped most of your testing. On that release, a late boss fight introduced a soft lock that roughly 1 in 15 players hit. A missing level would have hurt reviews far less than a broken one. Our rule now is a hard content freeze four weeks before launch. After that date, the only changes allowed are bug fixes and text corrections. Anything else goes into the first update, which also gives you a reason to post news two weeks after launch.
Keep the checklist alive after launch
After each release, spend 30 minutes adding whatever surprised you to the list. Our checklist started at 18 items and is now at 41, and almost every new line exists because something went wrong once. That is the real value of the list: it is a record of your studio's mistakes, written so you only make each one once. It also pairs well with tracking small milestones, since ticking off a whole release block is a moment worth marking with the team.
Frequently asked questions
How far in advance should you plan a game release?
For a small indie game, start the release checklist about eight weeks before launch. That leaves time for the store page, a full testing pass and outreach to creators. If you plan to show in a festival or event, add another four to six weeks.
What should be in a game release checklist?
At minimum: store page assets, pricing, clean install and minimum spec tests, save file tests, press and creator keys, launch announcements and a hotfix plan. Each item needs an owner and a due date. Add anything that went wrong on your previous releases.
What day of the week is best to release an indie game?
Most small teams choose Tuesday through Thursday so they have working days afterward to fix problems. Avoid launching right before a weekend when you cannot respond quickly. Checking competing releases that week matters more than the exact day.
More in Studio
Studio
Handling Player Support as a Two Person Game Studio
Our second game sold about 1,200 copies in its first three weeks, and we were not ready for the mail that came with it.
Studio
What a Small Game Studio Spends in Its First Year
Someone in our Discord asked what it costs to start a studio, and the answers he got ranged from nothing to thirty thousand...
Studio
How to Get Steam Wishlists Before Your Indie Game Launches
You put your game on Steam, shared the link once, and the wishlist counter has been stuck under 200 for a month.