PUSHB
Back to front page

Indies

How to find worthwhile new games on itch.io without chasing hype

A repeatable discovery method using official feeds, specific mechanics, transparent scope, and short hands-on tests.

By PushB Editorial DeskSep 2, 20266 min read
How to find worthwhile new games on itch.io without chasing hype

itch.io's openness is its advantage and its sorting problem. New releases include finished games, prototypes, jam entries, tools, assets, experiments, and uploads with almost no usable description. A good discovery process should preserve surprise while reducing noise—and it should never turn a store listing into an unearned review.

Use feeds as an inbox, not a ranking

itch.io documents RSS access for browse pages and maintains feeds for new uploads, featured games, and active sales. These feeds answer what appeared, not what is best. Treat them as raw leads that require human selection.

Begin with released games from a recent window, then separate playable games from assets and development tools. Exclude adult material when it does not fit the publication, but do not mistake an automated keyword filter for editorial judgment.

Look for a mechanic you can repeat clearly

Strong discovery candidates usually let you describe the player's central action and the pressure around it. Hang bells whose rings intersect. Move a card belt with a crank. Manage a shared resource across a tiny tactical grid. Specific verbs create testable expectations.

Genre labels are useful routing information but poor evidence of distinctiveness. 'Roguelike deckbuilder' describes a neighborhood; it does not explain why a player should enter this particular house.

Reward transparent scope

A useful listing identifies platform, status, price, input, session length, and what is unfinished. Development logs can reveal whether a mechanic survived iteration or merely appeared in marketing after the fact.

Production disclosures also matter. itch.io provides AI-disclosure fields on listings, and developers may add more detail in the description or credits. Readers should receive that information without the publication exaggerating or minimizing it.

Play before using review language

Discovery coverage can summarize the premise and explain why it is worth testing. A review requires firsthand play, a named build, enough time to reach friction, and clear test conditions. Browser availability makes this boundary easier to respect, not easier to ignore.

Use a short first test to check controls, feedback, readability, and whether the core decision actually appears. Continue when the game produces a durable question. Stop when the pitch has already been answered—or when technical problems prevent a fair test.

Build a healthier recommendation loop

Link directly to the developer, state whether inclusion was paid, retain source notes, and revisit promising projects after meaningful updates. A small publication can add value by following games that larger outlets notice only after popularity is already established.

The goal is not to predict a hit. It is to make overlooked work legible while protecting readers from fabricated certainty. That gap—between raw upload feeds and professional review—is where careful indie discovery belongs.

Sources and transparency

PushB independently selected and researched this topic. No publisher, platform, team, or developer paid for inclusion. Release information can change; linked primary sources should be treated as the latest authority.

Frequently asked questions

Does itch.io have an RSS feed for new games?

Yes. itch.io documents a new-upload feed and allows .xml to be appended to browse-page URLs.

Are new itch.io listings reviewed?

A listing is a developer storefront page, not an independent review. Evaluate its scope and play the available build before making quality claims.

Continue reading

More from PushB