Web portals reject most indie games with a sentence instead of a reason. In November 2026, a developer on r/gamedev reported that CrazyGames turned down their finished, working multiplayer game with the line "quality does not yet meet the expectations" and nothing else. The explanation is structural: a portal is a curated storefront drowning in supply — Poki says it sustains about 100 million monthly players with roughly 500 developers — so your submission lives or dies in its first thirty seconds of gameplay, long before anyone evaluates what you spent months building.
That sentence is uncomfortable, so let's be transparent about who's telling you this: Egmatic is a pre-alpha AI-native game-building tool, and this blog is how we think through the publishing layer indie developers actually face. We're not a portal, we don't review games for one, and we have no stake in which portal you submit to. We do have a stake in you shipping a web game that clears review funnels like this one, because that's the layer we're building for. What follows is the picture assembled from the portals' own public statements, their published tooling, and what rejected developers have documented in November 2026.
This article is about the portal rejection funnel itself — CrazyGames, Poki, and the aggregators behind them. If you're still deciding whether the browser is the right venue for your game at all, that's a different question, covered in Browser Game or Steam? Where Your 2D Game Finds Players. And if your rejection pain is Steam's identity verification rather than a web portal, the Steam Direct 2026 walkthrough covers that funnel end to end.
Quick answer
Portals reject games because they run an attention business, not a game-hosting business. Their revenue comes from ad impressions inside engaged sessions, a weak game produces short sessions, and the supply of willing submissions vastly exceeds the number of new games a portal needs per quarter. So the review optimizes for one question: will an average player be playing, and enjoying it, within seconds of arrival? Everything else — engine, art style, even originality — is secondary to that first impression.
The rejections developers actually receive map to a short list of underlying causes:
| The rejection you see | What it usually means | The fix that addresses it |
|---|---|---|
| "Quality does not yet meet the expectations" — no reasons given | The first-session experience is weak: slow start, unclear loop, or rough polish | Cut everything between landing and gameplay; sharpen the core verb |
| Weeks of silence, then nothing | Auto-fail on a hard requirement: load time, broken fullscreen, no ad SDK integration | Run the portal's own checklist before resubmitting |
| Accepted, but never featured | You cleared the floor, not the bar — the game runs but doesn't retain | Compare against the portal's current front page, not its minimum requirements |
| Rejected by top portals, accepted by aggregators | Different gates: curated portals judge hit potential, aggregators judge functionality | Treat the aggregator listing as a live prototype that earns you a stronger pitch |
The wording in the first row is real, by the way. In November 2026, a developer on r/gamedev reported that CrazyGames rejected their finished multiplayer web game with exactly that line — "quality does not yet meet the expectations" — and not a single concrete reason. The game worked. It had players on itch. The portal still said no, because "works" was never the question.
Why portals can afford to say no
Start with the numbers the portals publish about themselves. As of November 17, 2026, Poki's developer site describes a platform with 100 million monthly players and more than a billion gameplays per month — sustained by a community of roughly 500 developers. Sit with that ratio for a second: half a thousand studios powering a nine-figure audience, with Poki noting that a high-performing game alone can draw more than five million monthly players.
The arithmetic explains the coldness. If one hit title can carry millions of monthly sessions, a portal doesn't need your game — it needs a hit, and it needs to find it cheaply among thousands of submissions. Adding a mediocre game doesn't just fail to add revenue; it actively dilutes the metric that keeps players returning: the odds that a random click leads to something fun. A curated portal's entire product is those odds.
That's also why the rejection letters are form letters. Personalized feedback costs reviewer time, invites debate, and creates zero revenue. A template costs nothing and quietly filters out developers who won't self-audit — which, from the portal's perspective, is a feature. You can resent this or account for it; only one of those produces a published game.
None of the portals publish a scoring rubric, so the practical checklist below is a synthesis of three sources: what the portals say about themselves publicly, what their own tooling is built to measure, and what rejected developers consistently report. It is the closest thing to a leaked answer key you will get.
What the review actually sees: your first thirty seconds
Imagine the reviewer's session, because it's barely a session at all. A build loads in a browser tab, next to a dozen other tabs, on a machine that may be a mid-range laptop. The reviewer gives it somewhere between thirty seconds and two minutes. In that window, this is what's visibly on trial:
Time to gameplay. Every second between the page loading and the player doing something is a second of drop-off the portal has measured a thousand times. Logo screens, studio intros, story cards, "click to start" walls stacked on loading bars — each one is a tax. Portals know the math because their business is sessions; a build that makes players wait is a build that costs money before it earns any.
One-input legibility. Can a new player act within seconds without instructions? Mouse-only or one-finger designs clear this bar; keyboard-heavy schemes and multi-key bindings fail it, especially since portals distribute heavily to mobile web. If your game needs a tutorial to explain its controls, the controls are the bug.
Muted by default. A large share of portal players arrive with sound off — office tabs, school Chromebooks, late-night phones. A game whose feedback lives in its audio dies quietly in review. Visual feedback for every state, captions where audio carries meaning.
A visible loop. Within thirty seconds the reviewer should be able to name the verb and the reward: I dodge, I score, I stack, I win coins, the tower grows. Games where the point emerges at minute five have a place in the world. This is not that place.
Touch and window fitness. Does it run in a 16:9 browser window, at a portal's embedded dimensions, without breaking? Does it survive a mid-tier Android phone's browser? Keyboard-only plus fixed resolution is the classic auto-reject nobody announces.
The failure path. What happens when the player dies or loses? A fast, legible retry keeps sessions alive; a slow game-over screen or a restart that re-runs the intro bleeds them. Reviewers watch the death flow because it's where retention is won.
Poki, notably, doesn't even pretend this is mysterious. As of November 2026 its developer offering leads with Playtesting — "experience your game through the eyes of real players" — and lists in-house QA among what it handles for developers. Read that as the portal telling you the rubric: they will judge your game the way players do, quickly and without mercy, so use the playtest tooling before they have to.
What to do after the rejection lands
A rejection with no reasons is still information. It says: somewhere in the funnel above, your build didn't clear. Here is the sequence that turns that into an acceptance, in the order that pays off.
- Re-run your own first thirty seconds — on strangers. Not friends, not fellow developers; they forgive what players won't. Watch silently. Count seconds to first input. Note the exact moment attention drifts. That moment is your rejection reason, delivered free.
- Cut the opening to the bone. Landing straight into gameplay, or one tap away, is the single highest-leverage change a rejected build can make. Every screen you delete raises the ceiling of everything else.
- Test the hostile conditions. Muted audio, a window resize, a mid-range phone, a refresh mid-session. Fix what breaks. This is also where the technical floor lives: portals expect games that persist and run without you operating a backend — how browser games save data without a server covers the local-storage patterns reviewers implicitly assume.
- Benchmark against the portal's front page, not its rules. You are not competing with the minimum requirements; you're competing with today's featured games for the same slot. Open the portal, play three front-page games, and be honest about the polish gap. That gap, not a checklist item, is usually what "quality" meant.
- Resubmit with visible changes. Portals accept resubmissions; what they don't reward is an identical build or an appeal letter. Change things a player would notice, say so in the submission notes, and submit again. Games do get in on attempt two or three.
- Run your own web demo in parallel. A playable URL you control — your own page, not only an itch listing — is the asset that makes portal decisions matter less. It's also your pitch: "here, play it" beats any form letter. The playable web demo guide walks through hosting one.
- Climb the ladder. Submit to the top portals, but expect your first yes from an aggregator or mid-size portal. A game with live playtime evidence is a categorically different resubmission case — and if the portals never say yes, the aggregator route still puts the game in front of players.
Portal snapshot: who gates what
The practical difference between the venues, as of November 17, 2026:
| Venue | What they publicly emphasize | What that means for your submission |
|---|---|---|
| Poki | 100M monthly players, 1B+ gameplays/month, curated community of ~500 developers, in-house QA, Playtesting with real player data | The highest bar. Apply with a finished, touch-ready, instantly playable build; use their playtest tooling first |
| CrazyGames | Developer portal for publishing Unity and HTML5 web games with ad revenue share | Curation with a documented form-letter rejection pattern; community reports say the bar has risen as supply grew |
| Aggregators (GameDistribution, GamePix and similar) | Open catalogs distributing across many partner sites | Lower functional bar, thinner per-game traffic — the realistic first listing and a live prototype for later pitches |
One caution on reading that table: portal programs change their terms often enough that anything older than a quarter deserves re-verification, and the aggregator column in particular reflects common developer experience rather than a published policy. The portals' own developer pages are the live truth — CrazyGames at developer.crazygames.com, Poki at poki.dev.
Five mistakes worth avoiding
Submitting a vertical slice as a finished game. Portals review what ships, not the roadmap. If the polished part is three levels deep behind rough ones, the reviewer quits before arriving.
Designing for the desk you built it on. Keyboard-only controls, fixed resolutions, audio-dependent feedback — each assumes a context portal players don't have. The build has to survive the hostile conditions first.
Reading a rejection as a verdict on the game. It's a curation decision made in under two minutes, on supply-demand terms, about one build's first impression. Plenty of games with devoted audiences on itch have a drawer of portal rejections. The funnel filters for portal-fit, not for worth.
Arguing instead of iterating. The reply that explains why the reviewer was wrong changes nothing. The resubmission where the first thirty seconds are visibly different changes everything.
Making portals the plan. The stronger sequence runs the other way: your own playable URL first, a real audience second, portals as amplification third. The developers who negotiate well with portals are the ones who arrived with data. The publishing cluster starts with publishing to every platform from one project — portals are one channel in that stack, not the gatekeeper of whether your game exists.
Where Egmatic fits
There's a version of this story where the rejection feels personal because the whole pipeline collapsed your months of work into one opaque sentence. The layer we're building attacks the part before the sentence: getting a web-first build that's playable, touch-ready, and hosted somewhere real, without a programming team.
The frame matters, so we state it plainly: you direct, it executes, you own it. Design decisions stay yours; the AI teammate does the build work under your direction; every exported file is yours, portal-ready, no lock-in. We're pre-alpha and say so — early access today means build news, not promises of magic. But the direction is exactly the wedge this article describes: a game you can put in front of strangers in minute one is a game that survives minute-one review.
If that's the pipeline you want, early-access news lands a handful of times a year:
Fact-check notes
Checked November 17, 2026, against live pages and current community documentation:
- Poki scale and model claims (100M monthly players, 1B+ gameplays/month, ~500-developer community, 5M+ monthly players for a high-performing game, in-house QA, Playtesting, seamless monetization): poki.dev, fetched live November 17, 2026.
- CrazyGames submission model ("Publish Unity and HTML5 web games and earn revenue"): developer.crazygames.com page title/meta, fetched live November 17, 2026.
- The "quality does not yet meet the expectations" rejection wording and the no-reasons-given pattern: r/gamedev thread reported in the Egmatic feedback digest, sweep of November 11, 2026.
- Steam verification contrast (KYC reported at up to 45 business days): same r/gamedev sweep, November 2026; full Steam funnel covered in our Steam Direct 2026 walkthrough.
- The "first thirty seconds" review framing: editorial synthesis — no portal publishes a rubric; sources are the portals' public self-descriptions (Poki Playtesting, in-house QA), their tooling, and consistent developer reports. Labeled as synthesis in the text.
- Aggregator characterizations: common developer experience, explicitly hedged in the text as such; no published policy was verifiable for GameDistribution or GamePix as of this date (their developer pages are behind client-side rendering).