Inside PlayKovo: How We Review HTML5 Game Submissions

When you upload an HTML5 game to PlayKovo, it goes through a fixed review before anyone can play it. This article explains what happens at each step, what the reviewers look at, why games get rejected, and gives you a checklist to run before you submit. It describes the process as written in PlayKovo's public submission rules, which are the authority if anything differs.

1. Automated checks. Your ZIP is unpacked, its structure is validated, every file type is checked against an allowlist, and the whole bundle is scanned for malware before it is ever served to a player.
2. Human play-test. A moderator opens the game, plays it, and compares it against your store listing on both desktop and mobile.
3. Decision. You get an email either way. A rejection names the specific reason so you can fix it and resubmit, and resubmitting costs nothing.

Your build stays private throughout review. After approval, you keep ownership; PlayKovo gets the right to host and display the game while it is published, and nothing more.

Package and structure

• A playable HTML5 ZIP with index.html at the root or inside a single top-level folder, or a stable HTTPS URL that can be embedded.
• Limits: 250 MB compressed ZIP; 600 MB and 500 files once extracted. Bigger games should be hosted by you and submitted as an external HTTPS embed.
• Unity, Godot, GameMaker, Construct, PlayCanvas and Flutter web exports are all accepted.

File types and code

• Only allowed file types are accepted; unusual or hidden files are refused.
• Obfuscated code that hides what it does, and network calls to outside servers that send player data off PlayKovo, are rejected.
• Third-party ad SDKs inside the build are not accepted. Ads on developer-submitted games are not active at the time of writing; the rules page states this plainly.

Listing assets

• Thumbnail: square, 512x512, up to 2 MB.
• Cover: 16:9, up to 4 MB, WebP preferred.
• Preview video: up to 20 MB and 20 seconds, MP4 or WebM.

• It starts. No blank screen, no console errors on load, and the first level is playable.
• It matches the listing. Thumbnail, cover, video and description must show the game the player actually gets: no borrowed footage and no screenshots of a different game.
• It works on a phone with touch controls and the orientation you declared, unless you marked it desktop-only.
• It is safe for a broad audience. PlayKovo is built for a family-safe audience, so ads, monetization and external links must hold up for all ages.
• Ad behavior is clean. No forced redirects, fake buttons or fake close icons, and no popups outside the game frame.
• You have the rights. Code, artwork, audio and fonts must be yours or properly licensed.

The submission rules list the common reasons. Below, each one is paired with an anonymized example of the kind of situation it describes. These are illustrative scenarios, not quotes from specific developers.

Reason	What it looks like	Fix
index.html missing, or only runs from a local path	A build exported with absolute C:/ or /Users/ paths for assets	Use relative paths and test by serving the folder from a web server
Blank screen or console errors on load	A script requests a file that is not in the ZIP	Open DevTools, reload, fix every 404 in the Network tab
Assets without permission	A music track or character sprite taken from another game	Replace it or attach a license that covers redistribution
Disruptive ads	A banner covering the play area, or a button styled like a system dialog	Remove the ad code and use only the platform's approach
Misleading listing	Cover art showing features the game does not have	Use real screenshots of the build
Data leaving the platform	An analytics script posting player IDs to an outside server	Remove the tracker
Prohibited content	Real-money gambling mechanics, adult or shock content	Not eligible; this one cannot be fixed by editing

• Serve the extracted folder from a local web server and play it through once, start to first level end.
• Check DevTools for 404s and console errors; there should be none on load.
• Check there are no absolute local file paths in the build.
• Test on a real phone in the orientation you declared; if desktop-only, mark it.
• Remove ad SDKs, trackers and any calls that send data to outside servers.
• List the source and license for every font, sound and image.
• Make the thumbnail 512x512, the cover 16:9, and use screenshots from the real game.
• Write a description and controls text that match what players will see.
• Confirm you can show permission for any third-party code or assets.
• Check size limits: 250 MB ZIP, 600 MB / 500 files extracted.

If you replace a hosted build, or an external URL starts serving different content, the game can be reviewed again. A game can be unpublished if it breaks the rules, a rights holder disputes it or it becomes unplayable, and you can ask for yours to be unpublished at any time.

Ready to send a game? Start from the developer area, and read how plays are counted in why game portals count plays differently so the numbers you see make sense.