Direct file management
Create files in the dashboard, upload individual assets, or upload a ZIP archive when a project is ready to publish.
Features
Upload HTML, CSS, JavaScript, images, PDFs, and other static assets, then publish them as a versioned StaticX site.
Create files in the dashboard, upload individual assets, or upload a ZIP archive when a project is ready to publish.
StaticX expects an index.html for the homepage and encourages a 404.html so missing pages render cleanly.
Editing updates the working files. Publishing creates the next immutable version for rollback, analytics, and production history.
Use direct file upload for simple websites, client edits, and AI-generated pages that do not need a build step.
Keep index.html at the root and include CSS, JavaScript, images, PDFs, and 404.html beside the paths that reference them.
Use the dashboard file manager for small changes or upload a ZIP when the whole tree is ready.
Saving edits changes the working files. Publishing creates the immutable release used for rollback and analytics.
A one-page HTML site can still be production work. StaticX treats uploaded files like a real release, not a temporary pastebin.
That means you can edit a typo in the browser, publish a clean version when ready, connect a domain, collect form submissions, and roll back if the change breaks the page.
A custom 404.html keeps broken links professional and helps agents build complete static sites.
Small changes can be made in the dashboard without rebuilding a ZIP from scratch.
Publish only when the working files are ready to become production history.
Short, practical answers for using this page safely.
Yes, but production sites should include index.html and preferably 404.html plus any referenced assets.
The edit updates the working copy. Create a new deployment version when you want rollback, analytics, and history to track the change.
Yes. Add StaticX form rules to normal HTML forms so submissions appear in the lead inbox.