1. Your creator account
When uploads open, we email everyone on the creator list a link to set up a creator account with the address they registered. If you already have an Intellegamilandia player account with that address, it becomes your creator account; otherwise you create one in a minute.
- A free plan to start. Publish your first games at no cost.
- Paid plans when you need more: more published games, bigger builds, longer analytics history, CSV export and team seats. Plans and prices will be announced before uploads open, and registering early never commits you to one.
- Your creator profile shows your name or studio, a short bio, a link to your website and all your published games. Players can follow it.
2. Preparing your build
Games are uploaded as a single .zip file of your web export.
index.html at the root of the zip. If everything sits inside one folder (MyGame/index.html), that folder is used as the root automatically.
- Relative paths only:
./assets/hero.png, not /assets/hero.png. Each version of your game is served from its own folder, so paths starting with / point to the wrong place.
- Standard zip compression (deflate or stored). Password-protected zips can't be checked, so they are refused.
- Not allowed: server-side code (
.php, .py, .sh, .htaccess…), programs and installers (.exe, .dll, .apk, .jar…) and symbolic links. Files are checked by their contents, not just their names.
- Skipped automatically: system clutter such as
__MACOSX/, .DS_Store, Thumbs.db and .git/.
- Size limits depend on your plan. The free plan is planned at 100 MB per zip, 250 MB unpacked and 2,000 files; paid plans go much higher. The upload screen will always show your limits.
- Big uploads are safe: large archives go up in parts, so a dropped connection only repeats the part that failed, and you can resume where it stopped.
3. Supported engines
Any game that runs in a modern browser works. The engine is detected when you upload, and you can change it in your game's settings.
| Engine | What to know |
| Plain JavaScript, Canvas, WebGL | Works as it is. Keep every file inside the zip. |
| Phaser, PixiJS, three.js, PlayCanvas | The standard web build works. Bundle your libraries rather than loading them from another site, so the game also works offline after the first play. |
| Construct, GameMaker | The default HTML5 export works. Test it in Preview before you submit. |
| Godot 4 | Both exports work. Builds with threads are detected and play in a dedicated player page that allows them; builds without threads (untick Thread Support in Godot 4.3 and later) play right on the game page and start a little faster. |
| Unity (WebGL) | Pre-compressed Build/*.br and *.gz files are served with the right encoding, so you don't need Decompression Fallback. |
| Multithreaded WebAssembly | Detected when the build ships a *.worker.js next to its .wasm; otherwise switch on Multithreaded build in the game settings. Keep all files inside the zip. |
4. Where your game runs
Your game plays in a sandboxed frame on a separate domain. That keeps players safe, and it keeps your game safe from everything else on the page.
Works
- JavaScript, WebGL and WebGPU, WebAssembly, Web Audio, Canvas
localStorage and IndexedDB for saves, private to your game
- Fullscreen, from our player button or your own call
- Pointer lock, gamepads, device tilt, keeping the screen awake, sound that starts on its own
fetch and WebSockets to your own servers for leaderboards or multiplayer, when they allow your game's domain (CORS)
Blocked
- Pop-ups and new windows (
window.open, target="_blank")
alert, confirm and prompt: use in-game messages instead
- Redirecting or changing the page around your game
- Camera, microphone, location, payments and USB
- Reading anything from the arcade's page, its cookies or its storage
Layout: make the game fill its frame and follow resize events. This is usually all it takes:
html, body { margin: 0; width: 100%; height: 100%; overflow: hidden; }
In your game's settings you set the aspect ratio, the orientation and whether it works on phones. The player uses them for sizing and fullscreen, and phone players see a notice when a game isn't marked as phone-friendly.
5. Talking to the arcade
No library is needed. Your game can send three optional messages to the page around it:
function arcade(type) {
try { window.parent.postMessage({ type: type }, "*"); } catch (e) {}
}
// 1. Your game has loaded and is ready to play: hides our loading screen.
arcade("platform:ready");
// 2. The player finished the game (beat the last level, completed a run...).
// Counted once per play session; it powers the "completions" number.
arcade("platform:complete");
// 3. Your game can't start (missing files, unsupported browser...):
// shows our error screen with a "Try again" button.
arcade("platform:error");
Without platform:ready, the loading screen closes when your page's load event fires, but sending it once your assets are ready looks smoother. The messages carry no data, and the arcade only accepts them from your own game's frame.
6. Analytics
All numbers are recorded by the arcade itself, so you add nothing to your build. There are no third-party trackers, and we never store players' IP addresses or locations in analytics.
| Number | How it is counted |
| Views | Visits to your game page, counted once per visitor within a time window. Bots are left out. |
| Plays | Each press of Play, counted once per visitor within a time window. |
| Unique players | Different people who played, whether signed in or not. |
| Playtime | Time the game was on screen, checked against real elapsed time. |
| Completions | platform:complete messages, at most one per play session. |
| Devices | The share of plays on phones, tablets and computers. |
| Community | Ratings, reviews and followers of your creator profile. |
The free plan covers the last 7 and 30 days. Paid plans add 90 and 365 days, the device breakdown and CSV export.
7. Review and content rules
Every game is checked by a moderator before it goes live. Test yours in Preview first: it is exactly the same sandbox players get.
🎯 Skill games only
Intellegamilandia is an arcade of skill games, and every game on it has to be one. Results must come from the player's decisions, timing, logic or knowledge. That means:
- no betting, wagering or games that imitate casino games (slots, roulette, card games for stakes)
- no prize draws, loot boxes or paid random rewards
- nothing that pays out money, prizes or anything else with a cash value
A little randomness is fine when skill decides the outcome, such as a shuffled level or the next tile in a puzzle.
Moderators also check that:
- the game loads and can be played in the player;
- the title, description, cover and screenshots match the game;
- there is no malware, crypto-mining, phishing, and no attempt to collect passwords or personal data;
- the content suits a general audience: no sexual content, graphic violence, hate or harassment;
- you own the rights to the game and everything in it (art, music, fonts, names);
- there are no misleading redirects and no ads disguised as gameplay.
8. Updates and versions
- New builds: every upload becomes a new version stored at its own address. If the game is live, the new version goes to review while players keep the current one, so the game never goes offline for an update. There is no cache to clear.
- Game page edits (title, descriptions, tags, category, cover, screenshots) go live straight away. A moderator looks at them afterwards and can restore the previous version if something breaks the rules; you get a notification if that happens.
- Version history: earlier versions are kept for a while, so you can see what changed and when.
- Unpublishing: you can take a game down or delete it at any time.
9. Working as a team
On paid plans you can invite people to work on your games, each with a role:
- Manager: everything to do with games, including publishing, unpublishing and deleting.
- Developer: edits game pages, uploads builds and sends them to review.
- Analyst: sees the numbers, changes nothing.
Earnings, billing, the team itself and your public profile always stay with the account owner.
10. Earning and payouts
Planned terms. The final terms will be in the creator terms published before uploads open.
Revenue that comes from your games is split 90/10 in your favour, worked out on net revenue: what remains after payment provider fees, refunds and chargebacks. Your dashboard will show the split for every transaction.
Example: €100 of revenue from your games
- Revenue
- €100.00
- Payment provider fees
- −€3.20
- Net revenue
- €96.80
- Platform share (10%)
- −€9.68
- You receive
- €87.12
- Where revenue comes from: revenue sources such as advertising around games, paid games, in-game items and player support will be switched on one at a time. Your earnings only ever show money that has actually been received.
- Holding period: new earnings are held for a short time to cover refunds and chargebacks, then become available.
- Payouts: once your available balance reaches the minimum, you ask for a payout to your bank account or another supported method. Before the first payout we confirm your identity and payout details, as our AML Policy requires.
- Your rights: you keep all rights to your games. You only give us the permission we need to host and show them, and that ends when you remove a game.