PRACTICAL GUIDES
How to edit one HTML file without uploading a whole website
A standalone HTML file can be enough for one content update when its styles are included and it does not depend on missing local resources. Follow the actual import → edit → save → export workflow, and check these limits before subscribing.
Choose HTML when the page is genuinely standalone
From Connect a website, upload one UTF-8 .html or .htm file up to 10 MiB. Your workspace's project and storage limits still apply. Uploading about.html creates a project containing about.html; it does not silently rename it to index.html. Keep a copy of the original file.
Inline CSS travels inside the HTML. A reference such as assets/style.css does not bring that file from your computer. The importer does not reconstruct a missing logo, font or stylesheet. Uploading a page cannot make an unavailable remote service work.
Use a ZIP when local assets are required
If the page uses separate styles, local fonts, images or JavaScript, include them in a ZIP with their relative folders intact. For example: index.html, assets/style.css and assets/logo.webp. The archive may contain one page and its necessary resources, without unrelated pages.
A hosted-builder URL, React source folder or CMS database is not a static HTML export. Obtain the actual exported files first. The import checks paths, limits and page structure; a generator's name alone does not establish compatibility.
Make a small edit and confirm the save
Confirm your account, enter a project name, select your HTML or ZIP and import it once. The project card updates when ready; its thumbnail may finish later. Open the project, choose the actual filename and start with one paragraph in the preview or document outline.
Change the text, inspect the preview and press Save. Wait for the saved confirmation, reload and check the paragraph again. A changed preview is not a saved version. Imported source files remain separate from generated versions.
Understand safe preview and validation
Imported JavaScript is disabled in safe previews. Original script resources are retained in the export. A mobile menu that is inactive inside the editor therefore still needs testing on your own hosting. Editing its label does not repair a broken script or external API.
A missing H1 or title already present in the source is a warning, not a blanket rejection of every edit. Removing an existing heading or title, changing protected structure or introducing unsafe content may still be rejected. If saving fails, preserve the draft and copy its error reference; do not repeatedly submit or discard your work.
Export and inspect the actual file
Download Export ZIP and check that the edited page keeps its intended filename. Test text, asset paths, links and mobile behavior on your hosting before replacing the live page. StaticFrameLab does not automatically deploy the export to your host.
Try the downloadable standalone about.html sample first: it includes inline CSS and no H1. Its original ZIP and reviewed export show the exact paragraph change. These are tested synthetic demonstrations, not customer endorsements.
Examples and verification method
These instructions describe the current StaticFrameLab workflow. Examples are synthetic, tested with the real importer and editor, and downloadable for independent inspection.
Get the tested examples ↗