On this page

Publish a MiniUp Site

Publish a MiniUp Site from the Publish page by pasting HTML, uploading an HTML file, folder, or ZIP, or deploying a public GitHub repository. MiniUp gives the Site a URL you can open and share.

Prepare your Site

Sign in first if you want to manage the Site from Dashboard. Prepare a no-build static project with a main index.html. Check the upload limits shown on Publish; folder file counts and per-file limits apply even when files arrive in a ZIP.

Publish HTML or a project

Open Publish.
Choose the HTML input, HTML file upload, folder upload, or ZIP upload for your content.
For pasted HTML, supply a complete document. For a folder or ZIP, include the main page and all local assets with their relative paths.
Enter the Site name and resolve any availability or naming error. Names are 3–64 characters using letters, numbers, hyphens, or underscores; reserved names cannot be used.
Review the preview and access choice, then publish. Wait for the successful result before leaving.
Open the returned URL. Test images, navigation, forms, and data loading on the published Site.

Deploy from GitHub

Sign in to MiniUp and open Publish. Enter your app name and choose Deploy from GitHub.
Paste a public repository URL such as https://github.com/username/project and click Connect repository. No GitHub login is needed.
MiniUp selects the default branch. Choose another branch if needed, and a deployment directory such as /, /docs, /public, /dist, or /build.
Confirm that MiniUp detects index.html, then click Pull & Deploy. Open the returned Site URL and test its assets.

For an existing Site, open GitHub Source in its Dashboard workspace. Check for Updates shows whether a new commit or changed source setting needs deployment. Pull Latest republishes the source while keeping the same Site URL and settings. Settings changes the branch or directory, or disconnects GitHub without taking the Site offline. Saved deployments can be restored through Page settings → Revisions, subject to your account’s revision allowance.

Only static websites and existing compiled output are supported. MiniUp does not install packages or run npm builds. Choose the compiled output folder for React, Vue, Vite, and similar projects. Private repositories, symlinks, submodules, Git LFS files, and unsupported source files cannot be deployed. Hidden files are excluded. Account upload and storage limits apply. If GitHub’s public API rate limit is reached, wait and retry.

A failed GitHub import leaves the previous live Site in place. Files removed from GitHub are absent from the next deployed bundle. Deployment remains manual; GitHub pushes do not trigger automatic updates.

Copy a minimal HTML page


<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <title>My first MiniUp Site</title>
  <style>
    body { font: 18px/1.6 system-ui; max-width: 48rem; margin: auto; padding: 24px; }
    a { color: #174db1; }
  </style>
</head>
<body>
  <main><h1>Hello from MiniUp</h1><p>My first published page.</p></main>
</body>
</html>

Understand the Site URL and index.html

A Site URL typically looks like https://my-site.miniup.app. Copy the actual URL shown by MiniUp, especially when using a custom domain. The root opens the Site’s main page. Put index.html at the project root and keep links relative so the folder structure works after upload. Do not assume a source project folder is its publishable output.

Fix common publishing problems

Name unavailable: choose another name; do not repeatedly submit a reserved name.
Blank page: inspect the main HTML file and browser errors; remove dependencies on a local development server.
Missing styles or images: check relative paths and include the referenced files in the folder or ZIP.
Upload rejected: check format, file count, and size limits. Remove unrelated project files before retrying.

publish · upload · HTML · ZIP · folder · index.html · naming · GitHub · deploy