Are you an LLM? You can read better optimized documentation at /static-sites/upload-deployment.md for this page in Markdown format
Upload a deployment
Upload your site files directly to create a new deployment. You can upload a single HTML file for simple pages or a zip archive for a complete site with assets.
Before you start
- You must be signed in.
- You must have an existing static site. If you have not created one yet, see Create a site.
- Your files must be pre-built. Manual uploads do not support the Mincemeat Build Engine — you must compile your project locally and upload the final static output. (For automatic server-side builds, use a GitHub Deployment).
Upload a single HTML file
Use this option for simple, single-page sites.
- Open the site detail view.
- Select Deploy.
- Select or drag a single
.htmlfile into the upload area. - Select Upload and deploy.
- The deployment starts processing. When it finishes, the new deployment becomes the active version automatically.
Upload a zip archive
Use this option for sites with multiple files (HTML, CSS, JavaScript, images, and other assets).
- Open the site detail view.
- Select Deploy.
- Select or drag a
.zipfile into the upload area. - Select Upload and deploy.
- The deployment starts processing. Mincemeat extracts the archive, validates the contents, and uploads the files.
Zip archive requirements
Your zip archive must follow these rules:
| Requirement | Detail |
|---|---|
index.html at the root | The archive must contain an index.html file at the top level of the zip or at the top level of a single root folder. |
| No path traversal | File paths must not contain .. segments or absolute paths. |
| No symlinks | Symbolic links inside the archive are rejected. |
| No executable files | Server-side scripts and executable files are blocked. |
| Size limits | The archive and extracted contents must be within the platform size limits. |
| File count limits | The total number of files must be within the platform file count limit. |
If your archive fails validation, the deployment is marked as failed with an error message explaining the issue.
What happens during upload
- Upload — your file is uploaded to secure storage.
- Validation — the archive is checked for structure, size, and safety (zip archives only).
- Extraction — files are extracted and stored under an immutable deployment path (zip archives only).
- Activation — the new deployment becomes the active version and your site starts serving the new content.
The previous active deployment is marked as Superseded but remains available for rollback.
What happens next
After a successful deployment:
- Visit your site URL to confirm the content is live.
- Check Deployment history to see all your deployments.
- If something is wrong, roll back to the previous version instantly.
Troubleshooting
| Problem | What to check |
|---|---|
| Upload fails immediately | Check the file type — only .html and .zip files are accepted. |
| Deployment fails with a validation error | Read the error message. Common causes: missing index.html, path traversal in zip, file too large, or too many files. |
| Site shows old content after deployment | Clear your browser cache or open the site in a private window. HTML pages are served with revalidation headers, but your browser may have a stale cached copy. |
| Deployment is stuck in processing | Wait a few minutes. Large archives take longer to extract and upload. If it does not complete, check the deployment detail for error messages. |