What Counts as an Indie Game? A Practical Evidence Checklist

Independently owned studio, self-published release and creatively autonomous team are different claims. Decide which one the discussion needs before gathering evidence. A reviewer, an awards entrant and a player choosing a game may legitimately need different answers.

Also identify the period. A game developed before an acquisition can have a different history from a sequel made afterward. Record the title, edition and development or release date alongside the claim so that current company information is not accidentally presented as the original production structure.

For ownership, prioritize corporate disclosures, acquisition announcements and clear studio statements. For developer and publisher roles, use release credits and official product records. For competition eligibility, read the organizer’s own rules rather than borrowing a fan’s interpretation of them.

The IGF provides an example of an event assessing independently created work with its own judging discretion. That is useful evidence about that event’s process. It should not be converted into a claim that the organization audits and certifies every game described as indie in a store or an unrelated awards show.

For the documented reference, see a concrete example of event-specific eligibility rules.

For each title, note the developer, publisher, known parent company, IP owner where documented and the date of each source. Add a brief conclusion that says what the records establish. Mark private or undisclosed details as unknown instead of filling them with a plausible story.

This can be a simple table or a few notes; it does not need a numerical indie score. A scoring system that awards points for pixel art or a small credits list can create a false precision. The relationships themselves are more useful than an invented threshold.

An independent studio with an external publisher is not automatically a subsidiary. A small team inside a large publisher is not automatically independently owned. A self-published game from a corporate-owned developer does not become independent solely because the same company performs both roles.

These examples expose the weakness of one-factor rules. If a definition produces a surprising result, explain the result rather than changing the definition for one favourite game. A consistent method makes disagreement clearer: readers can see whether they dispute the facts or prefer a different meaning of indie.

Sometimes the best available wording is independently developed with publisher-owned IP, or a corporate-owned team with substantial creative autonomy. These descriptions communicate more than forcing every game into a universal yes/no category.

Do not turn missing information into evidence either way. An undisclosed contract does not prove total freedom, and the absence of a publicly named investor does not prove self-funding. Explain the limit of the record while keeping the conclusions that are supported. Useful uncertainty is specific rather than vague.

Once the production question is answered, return to the game itself. Independence does not guarantee a particular genre, price, difficulty, support level or quality. Those details matter to a player but require their own review of the actual release.

For an editorial decision, a transparent evidence note is enough to make the classification reviewable. Update it if a later ownership announcement changes the relevant period. The goal is an accurate description that another reader can check, not a permanent purity badge attached to a screenshot.