Poki testing and release process, from upload to global release
Poki's published path for a new game: moderation, playtests, player and web fit tests, final review, QA, soft release, global release and post-release updates.
Poki splits its path into two halves. Testing is self-serve in Poki for Developers (P4D): you upload, run tests, and decide when to move on. Release starts only after Poki accepts the game in final review and offers an agreement. This page follows the steps and timings exactly as the P4D guide states them on 2026-10-01. For the deal terms and SDK summary, see the Poki portal page.
The path at a glance
| Step | What happens | Published timing |
|---|---|---|
| Content moderation | Each uploaded version is checked against content standards (adding your game) | Not published |
| Playtests | 10 recorded sessions from real players per test (playtesting) | First recordings often within minutes |
| Player fit test | 500 players, playtime only (player fit test) | About 5 hours; up to 2 per day |
| Web fit test | Real category pages; CTR, time on page, conversion to play (web fit test) | 3 to 5 days, or roughly 7 days (see below) |
| Final review | Poki reviews results and the game (final review) | 1 to 2 weeks |
| Agreement, QA, soft release, global release | Contract, requirement checks, limited then full launch (release process) | Roughly 2 to 3 months in total |
Every test is free and repeatable (how testing works).
1. Add your game and pass moderation
The build does not need to be finished. Poki says builds closer to its requirements give more useful results, and suggests running them through the Poki Inspector first, which shows fired SDK events, file size and loading time (adding your game).
Games not yet in QA, soft release or global release get a content moderation check per uploaded version before any test can run (adding your game).
2. Playtests
You choose devices and a category audience. A small group of Poki players sees a mystery tile and can opt in to a recorded session. Each playtest returns 10 recordings with the player’s inputs, console output, session length, country and device type (playtesting). The console output is the cheapest way to catch errors on devices you do not own.
The player fit test unlocks after you have watched at least 10 recordings (playtesting).
3. Player fit test
The game is shown to 500 players and only playtime is measured; nothing is recorded, and conversion to play is not part of this test. You pick a category and the mobile orientations, and you need a thumbnail uploaded once. A test usually takes around 5 hours and you can run two per day (player fit test).
The result is a playtime histogram. Poki calls a result healthy when average playtime is above 3 minutes and at least 25% of the 500 plays last more than 3 minutes. It describes 3 minutes as the bar to move on, not the target (player fit test).
4. Web fit test
The game appears on real category pages. Poki places it in several fitting categories; you can suggest up to four in Settings. Once started, a test cannot be stopped; to swap a buggy build mid-test, upload a new version and email Poki developer support (web fit test). The results guide puts the audience at around 10,000 players (reading results).
Three metrics count equally: click-through rate on the thumbnail, average time on page, and conversion to play (C2P). Each is scored 0 to 5 against the average of the categories tested, and a 3 means at or above that average (web fit test).
Duration conflict. The web fit test page says about 3 to 5 days, while the how testing works overview says roughly 7 days. Both add that busy periods take longer. Plan for the longer figure.
What the build needs at this stage:
- Clear the player fit test first.
- Fire
gameplayStart()correctly. C2P counts visitors who reach the firstgameplayStart()event, so a missing or early call corrupts the score (web fit test). The requirements say SDK events are required for web fit testing and all releases, and thatgameplayStart()must fire on the player’s first input, not on load (requirements). - Ads can wait.
commercialBreak()andrewardedBreak()are not required yet; if present they show placeholder ads and earn nothing (web fit test).
// Order from the Poki HTML5 SDK guide: init, loading finished, then
// gameplayStart on the first real input, not on load.
PokiSDK.init()
.catch(() => {}) // Poki's sample loads the game either way
.then(() => loadAssets())
.then(() => {
PokiSDK.gameLoadingFinished();
window.addEventListener('pointerdown', () => PokiSDK.gameplayStart(), { once: true });
});
The calls are from the HTML5 SDK guide; loadAssets stands in for your own loader. More on event order is in Poki SDK gameplay and commercial breaks, and the SDK event order checker flags repeated events in a recorded session.
A passing game is submitted to final review automatically. Until then it stays live on the test pages, unpromoted and earning nothing; you can ask Poki to remove it (web fit test).
5. Final review
The Poki team looks at the test results and the game itself: quality, originality and craft, and whether it is distinct enough within its categories. A decision takes 1 to 2 weeks. A game that does not pass cannot be published on Poki (final review). The results guide lists declines for originality, content safety, and categories already well covered (reading results).
After the green light
The release process has four steps:
- Agreement. Poki’s legal team prepares the contract.
- QA. After signing, support opens QA and checks the game against the requirements. Failing builds get a QA report; you fix, upload and request review until it passes.
- Soft release. Scheduling a slot usually takes 1 to 2 weeks. The game goes out on relevant category pages, not the homepages, for about 2 to 3 weeks, and this phase cannot be skipped. Poki expects you to watch conversion, errors, ad volume (at least one ad per daily active user) and player feedback, and to ship fixes through the same upload-and-review flow.
- Global release. Moving from soft release to global release usually takes 2 to 3 weeks, depending on performance and how fast you optimize. The game enters the promotion system, gets a push of around two weeks as a new game, and shows a fire icon on its thumbnail.
Static and animated thumbnails are both required for global release (requirements).
Post-release updates
After release you upload new versions through P4D and set them live. Poki suggests performance fixes, content updates and new languages, and asks you to talk to your Poki contact first about major content drops, sequels or changes of direction (post-release updates).
What to check before each stage
- Before the first playtest: build runs in the Inspector with no console errors; desktop, mobile and tablet all work.
- Before a player fit test: 10 recordings watched, thumbnail uploaded, early-game drop-off points fixed.
- Before a web fit test: player fit test cleared,
gameplayStart()on first input, no doubled SDK events, initial load as small as you can get it. - Before QA: the hard requirements met, including no external requests or ads, incognito-safe storage and play with an ad blocker (requirements).
- Before global release: animated thumbnail ready.
What is not published
Poki does not publish the score that passes a web fit test, how long content moderation takes, or the terms of the agreement offered after final review. The playtime and conversion figures it suggests aiming for are guidance, not stated pass marks. The web fit test duration differs between two of its own pages, as noted above.
Questions
- Do I need ads integrated for the Poki web fit test?
- No. Poki says commercialBreak() and rewardedBreak() are not required yet at that stage; if present, placeholder ads show and nothing is earned. gameplayStart() is needed, because conversion to play is measured against it.
- How long does the web fit test take?
- Poki's pages disagree. The overview gives roughly 7 days; the web fit test page gives about 3 to 5 days. Both say it can take longer when busy.
- Can I skip soft release on Poki?
- No. The release process page says the soft release phase cannot be skipped. It usually runs about 2 to 3 weeks.
Sources
- How testing works (Poki for Developers guide)
- Adding your game (Poki for Developers guide)
- Playtesting (Poki for Developers guide)
- Player fit test (Poki for Developers guide)
- Web fit test (Poki for Developers guide)
- Interpreting your test results (Poki for Developers guide)
- Final review (Poki for Developers guide)
- Release process (Poki for Developers guide)
- Post-release updates (Poki for Developers guide)
- Requirements and quality guidelines (Poki for Developers guide)
- Poki Inspector (Poki for Developers guide)
- HTML5 SDK (Poki for Developers guide)