Your Construct 3 game can live at its own address, ready to play as soon as someone opens the link. Export for the web, drop the playable files above and share the HTTPS URL. You don't need a repository or a terminal to try it.
How it works
- Export from Construct 3. Choose the Web (HTML5) export in the export dialog. Download the export and extract the ZIP so you can see
index.htmland its accompanying files. - Drop the export here. Upload the folder containing
index.html, or its ZIP. If you prefer a terminal, extract it intoexport/and runnpx lobsite ./exportfrom the folder above. The first link lasts 6 hours without an account. - Keep your game online. Choose Keep it free → to claim the game. Upload the next export to that same site when you update it.
Upload the export, not the project
A .c3p file is an editable Construct project, not a browser game. Lobsite needs the HTML5 export with its scripts, media and other generated files. Keep the directory structure intact and don't move just index.html out of the folder.
If your export includes offline support, its service worker may keep a previous version cached in a tester's browser. Check an update in a fresh browser session when diagnosing an old build. Construct's publishing documentation explains its export options.
Check media and file count
Construct games can contain many separate images and sounds. Free allows 100 files, 50 MB total and 5 MB per file. Check the extracted export: the size of the ZIP alone doesn't tell you whether each deployed file fits.
The box on this page accepts up to 25 MB at once. For a larger folder within your plan, use the CLI or sign in and upload from the dashboard. Standard increases the limits to 10,000 files, 2 GB total and 100 MB per file. The HTML5 game limits cover bandwidth too.
Share a level before release
Publish a separate playtest with npx lobsite --preview after keeping the site. That leaves your live game in place while testers check a new level. On Standard, a site password covers its live and preview addresses.
Before sharing widely, test touch controls, screen resizing and sound after the player's first interaction. Free's Lobsite badge sits in the bottom-right corner, so keep essential game controls clear of that area.
A deploy without an account is live for 6 hours. The claim link keeps it, free.
Preview before going live. Roll back in one click, redirects and all.
Files are stored by their hash. Redeploying an unchanged site uploads 0 bytes.
Every site gets a *.lobsite.app address with HTTPS from the first deploy.
Free accounts included: add one DNS record and the site moves to your domain. Every site has HTTPS on any plan.
Redirects, headers and forms live in lobsite.toml and travel with each deploy.
Ways to share a Construct game
| What you share | What the recipient needs | Best use |
|---|---|---|
| A Lobsite game URL | A compatible browser | Players and remote playtesters |
| The HTML5 export ZIP | A way to host the files | Handing a release to another publisher |
| The Construct project | Construct and any required addons | Collaboration on the editable game |
For another visual game editor, see GDevelop hosting. For coded browser games, see Phaser hosting.
Frequently asked questions
Can I upload a Construct .c3p file to play it online?
No. Export the game as Web (HTML5) first. Upload the resulting playable folder or ZIP, not the editable project.
Do I need the Lobsite CLI for a Construct 3 export?
No. The drop box can publish a folder or ZIP within its 25 MB upload limit. The CLI also supports updates and separate preview deployments.
Why does my Construct export pass the size check but exceed the file limit?
File count and storage are separate limits. Lots of small media files can exceed Free's 100-file allowance even when the whole game is under 50 MB.
Does Lobsite provide Construct multiplayer signalling?
No. Lobsite serves your exported game files. Multiplayer signalling and any other online services must be provided separately and configured in your project.