DeConstruct

DeConstruct isn't an official Construct exporter, doesn't copy anything from its runtime, and doesn't promise full behavioral parity. It's a migration assistant: it reads a Construct 3 project's structure and hands back what it can convert into plain HTML, CSS, and JavaScript, and honestly reports what it couldn't. It's built for projects the visitor themself owns, not for opening someone else's game.

I have years of games made in Construct 3, and no good way to get them out of there. DeConstruct was born from that need: it loads a project folder or a .c3p file, builds a normalized model of what it found inside (layouts, objects, events), and generates the closest possible version in readable vanilla code, understandable by anyone who knows HTML, CSS, and JavaScript.

The report it generates alongside is the most important part: it shows exactly what was converted and what was left out, so whoever finishes the migration by hand knows where to pick up.

Choose your Construct project folder or a .c3p file (direct .c3p support in the browser depends on the browser; the tool warns you if it can't). It builds a project summary and a Markdown inspection report, ready to copy or download. If you want to go beyond the report, the export-rebuild buttons generate an attempt at a real vanilla project, with an honest warning about what didn't fit.

Everything happens in your browser. DeConstruct reads the project files locally, processes everything in memory, and generates the report and the code right there: nothing is sent to any server, not ideabob's, not anyone else's. Close the tab, forget it ever happened.

Construct is great for prototyping fast, but it traps the game inside it: without exporting to real code, there's no way to take what I already built somewhere else. DeConstruct is my attempt to open that door, without pretending it's easier than it is. It gets things wrong, tells you when it does, and leaves the rest of the work to whoever understands their own project.