Technical requirements
AI Summary
A short gist of this page, generated for you.
Powered by AI. Summaries can miss nuance — when in doubt, read the page.
Your game must run smoothly on a wide range of browsers and devices. Design to the targets below.
#File size and loading
| Limit | Value |
|---|---|
| Game folder (total upload) | 100 MB or less — the Developer Portal does not accept more |
| Logo and other images | 5 MB or less each |
| Time to first interactive frame | 20 seconds or less on broadband; aim for under 10 |
Optimize aggressively
The smaller your initial download, the more players reach your game. See the optimization guide for engine-specific tips.
#Paths
- Use relative paths when referencing assets inside your game folder.
- Keep
index.htmlat the top level of the folder you upload. - Do not hot-link assets from external CDNs (Google Fonts, jsDelivr and so on). Bundle everything.
- The one exception is the Funox SDK itself, which must be loaded from
https://funox.com/sdk/v1/funox-sdk.js.
#Browsers and devices
#Desktop
- Chrome and Edge: must run smoothly at 60 fps.
- Safari: support is expected.
- Lower-end laptops with 4 GB RAM should still run the game.
#Mobile
- Must support touch input.
- Games should accept keyboard and mouse input on desktop even if designed for touch.
- You choose the orientation — landscape, portrait or both — when you upload the game.
#Aspect ratio
- Target 16:9 (for example 1280×720 or 1920×1080) and scale to fill the available space.
- The game runs inside a frame whose size changes with the player's screen, so never assume fixed pixel dimensions.
#Performance
- Hold a stable 60 fps during active gameplay on mid-range hardware.
- Avoid memory leaks — long sessions (over 30 minutes) should not degrade performance.
- Pause heavy work (
requestAnimationFrame, audio) whendocument.hiddenis true.
#Security and privacy
- Do not collect personally identifiable information without explicit consent.
- Do not load third-party scripts that were not agreed with us.
- Privacy notices must be non-blocking — they cannot prevent gameplay.
#Storage
- Wrap
localStorageaccess intry/catch; private-browsing modes can throw. - Cloud saves hold up to 100 KB per game per player — see Save data.
#Quick reference
text
game folder 100 MB or less
images 5 MB or less each
time to play 20 s or less
aspect ratio 16:9 (responsive)
target fps 60
low-end RAM target 4 GB
cloud save 100 KB