Download Your HTML, CSS and JavaScript Project
Download your HCODX project as a ZIP with HTML, CSS, JavaScript and assets. Check the exported paths before moving the files to another editor or host.
Export is a handoff from browser storage to files you control
Projects saved inside a browser profile are convenient for editing, but they are not a backup you can carry to another machine.
The HCODX main editor stores working projects in the current browser profile, primarily with IndexedDB and a localStorage fallback. Clearing site data, using a private session or changing devices can make that copy unavailable. Export important work regularly and keep the ZIP somewhere you manage.
A downloaded project is not automatically a live website. Static HTML, CSS, JavaScript and images can be hosted by a static site provider. Server routes, databases, secret API keys and form processing need a backend or another service.
Backup
Keep a dated ZIP outside the browser profile before clearing site data.
Handoff
Send ordinary files to a teammate or open them in another editor.
Deployment input
Use the unpacked front end as the source for a suitable static host or build workflow.
Check the tree and the paths before calling it finished
The ZIP should preserve the relationships between pages and their assets.
Open the archive and confirm the entry page is where you expect it. A page linked with href="styles/site.css" requires a styles folder beside that HTML file. Moving only index.html out of the archive breaks the relationship.
Open a self-contained page after unpacking. For pages that fetch data or depend on modules, file:// security rules can differ from a hosted origin; use a local server or staging host for the final verification.
project/
├─ index.html
├─ about.html
├─ styles/
│ └─ site.css
├─ scripts/
│ └─ app.js
└─ images/
└─ logo.svg
<!-- index.html -->
<link rel="stylesheet" href="styles/site.css">
<script src="scripts/app.js" defer></script>A four-step export check
A repeatable check prevents the most common “it worked in the editor” surprises.
If you continue in a different editor, keep one source of truth. Re-exporting from an old browser copy after desktop edits can overwrite newer work in your workflow.
A ZIP, a local folder and a published site are three different states
The same files can move through each state, but a successful download only proves the first handoff.
Downloaded archive
A snapshot you can store, inspect and transfer. It is the right artifact for backup or sending the source to another developer.
Unpacked project folder
Ordinary files you can edit elsewhere. Keep the directory tree together so relative links between pages, styles, scripts and images continue to resolve.
Published static site
Files served from a web origin. Test this state separately because absolute paths, case-sensitive file names, HTTP headers and network requests may differ from a local preview.
The asset path that breaks only after you move the project
A relative URL is resolved from the document containing it. Nested pages therefore need a different path to a shared stylesheet than the root page does.
In the tree below, index.html can load styles/site.css directly. The nested pages/guide.html is one folder deeper, so its link needs ../styles/site.css. Copying the root page’s link unchanged into guide.html makes the browser request pages/styles/site.css, which is not in the archive. The HTML still appears, making this easy to miss in a quick release check.
Avoid “fixing” the path with /styles/site.css unless you know the site will always live at the origin root. A leading slash starts at the host root, so it can fail when the exported project is published below a path such as example.com/demo/. Test the exact deployment location or use paths that match your host setup.
project/
├─ index.html
├─ pages/
│ └─ guide.html
└─ styles/
└─ site.css
<!-- index.html -->
<link rel="stylesheet" href="styles/site.css">
<!-- pages/guide.html -->
<link rel="stylesheet" href="../styles/site.css">Verify the extracted project, not only the ZIP filename
A release-ready archive should be understandable to someone who did not build it.
Extract into a fresh folder
Do not test from the editor’s original working state. A clean extraction reveals missing files and accidental references to files outside the package.
Open every document entry
Follow navigation from the homepage to nested pages. Confirm CSS, images and scripts load on each page, not only on index.html.
Inspect the browser network and console
Missing resources may leave a page partly visible. Failed requests and script errors make the problem explicit.
Test under the intended host path
If publishing below a subdirectory, preview there before sending the URL. Root-relative URLs and case mismatches may be invisible in the editor.
Project download questions
Make a copy that survives the browser
Export the project, inspect the ZIP and keep a dated backup outside your browser profile.
Instant HTML Runner & Viewer with Live Preview
Need to run a short HTML, CSS and JavaScript snippet? The HTML Runner Online has a focused editing surface with live output.
Open HTML Runner Online