Introduction
HTMLDrive solves a narrow problem. You have an HTML page or a Markdown note sitting in Google Drive, and you want it online at a link anyone can open. HTMLDrive opens the file in a browser editor, saves changes back to Drive, and publishes it to a public URL with one click. People who open the link don't need a login.
The site lists a single plan, which is free and capped at 10 published files. Nothing on the homepage covers custom domains, an API or build tooling. It came to our attention through Hacker News, and our overall rating is 5.4 out of 10. The score is held down by thin evidence on output quality and integrations, while ease of use scores high.
This review draws on the vendor's own site and FAQ plus one independent comment thread. We did not use the product ourselves, so feature claims below are attributed to their source.
Key Features
Browser editor for HTML and Markdown
HTMLDrive says it edits HTML and Markdown files from Google Drive directly in the browser, with syntax highlighting and a live preview. Per the homepage, you can switch between editor and preview modes. It handles those two formats only. The site does not mention CSS preprocessors, JavaScript bundling or any build step.
Auto-save back to Drive
Edits save back to the original file in your Drive, according to the site. Your Drive copy stays the source of truth, and the files stay in your own account instead of moving into a separate hosting dashboard. If your notes and drafts already live in Drive, this is the main reason to look at the tool.
One-click publishing
Publishing turns a Drive file into a public URL. The FAQ says anyone with the link can view the page without a Google account or signup. You can unpublish at any time, the public URL stops working immediately, and HTMLDrive says the cached copy on its servers is permanently deleted when you do.
Google OAuth 2.0 connection
You connect through Google OAuth 2.0, so you never hand over a password, and you can revoke access from your Google account settings. The FAQ also states that the service requests read/write access to your files. That scope is needed to save edits back to Drive, but it is a broad grant for a small third-party tool, and you should weigh it before connecting a work account.
Pricing Breakdown
| Plan | Price | What you get |
|---|---|---|
| Free | $0 | Up to 10 published files, browser editor for HTML and Markdown, Google Drive integration |
The free plan is the only plan the homepage shows. No paid tier, price or upgrade path is listed in the material we reviewed, and we could not find a separate pricing page. If you expect to need more than 10 live pages, you have no published figure to plan around.
For a personal project, 10 pages covers a resume, a couple of landing pages and a few shared notes. For a team publishing internal docs, or anyone who wants a small site with many pages, the cap will bite quickly.
Scores
| Criterion | Score (out of 10) | Basis |
|---|---|---|
| Ease of use | 9 | Browser editing with no setup, one OAuth connection to Drive, no separate signup |
| Pricing value | 6 | Free for up to 10 published pages; paid pricing not found |
| Problem fit | 5 | One-click publish and unpublish per the vendor; an independent commenter complained that deleting data requires emailing support |
| Output quality | 4 | Only the vendor's description of HTML and Markdown support and live preview; no independent samples |
| API and integrations | 3 | Google Drive only; no API, SDK or docs found |
| Overall | 5.4 |
The problem-fit score reflects a tension in the evidence. The FAQ says unpublishing deletes the cached copy, while a commenter on a zeli.app thread said that deleting your data means emailing support. These claims may refer to different things (a published page versus your account record), but the site doesn't clear that up, and no docs page turned up to settle it.
Pros and Cons
Pros
- Files stay in your own Google Drive, per the site, so you keep the original if the service disappears.
- Publishing is one click, and viewers need no account to open the page.
- Unpublishing kills the URL immediately and deletes the cached copy, according to the FAQ.
- The free tier needs nothing beyond authorizing Drive.
- OAuth access can be revoked from Google's settings at any time.
Cons
- The free plan stops at 10 published files.
- No paid plan or pricing is listed on the homepage, so there is no clear way to scale.
- It requires read/write access to your Drive files.
- Only HTML and Markdown are supported, with no stated support for build tools, custom domains or version control.
- No API, SDK or documentation page was found.
- An independent commenter reported that account data deletion goes through support email.
Who Is It For
HTMLDrive fits someone who already writes simple pages or notes in Google Drive and wants to share them as web pages with minimal ceremony. Examples include a one-page portfolio, an event page, a Markdown handout for a class, or an HTML prototype you want a colleague to click through. If you would otherwise paste content into a Google Doc and share the link, this gives you a real web page instead.
It is a poor fit for anyone building a site with more than a handful of pages, a project that needs a custom domain, or a codebase that goes through a build step. A visual site builder such as Framer or Wix makes more sense for marketing sites with design needs and domains. If you want an online editor that runs code and deploys apps, Replit covers far more ground. Developers comfortable with Git will find that a standard static host gives version history and domains that HTMLDrive does not mention.
Security-conscious teams should look hard at the OAuth scope first. Granting read/write access to Drive for a free tool with no published docs is a decision for whoever owns your Google Workspace policy.
Verdict
HTMLDrive does one thing, and the vendor describes it clearly. It turns a Drive-hosted HTML or Markdown file into a public page in one step, keeps the source in your Drive, and lets you pull the page down instantly. Its ease-of-use score of 9 reflects how little setup the process needs.
The rest of the picture is thin. The free plan caps you at 10 files, no paid plan is published, there is no API or documentation, and the data-deletion process has at least one public complaint against it. That adds up to a 5.4 overall.
Our recommendation: use HTMLDrive for personal, low-stakes pages from a personal Google account, where 10 files is enough and the Drive permission doesn't worry you. Skip it for team sites, client work or anything that needs a custom domain or version control, and use a full static host or a site builder instead. If HTMLDrive later publishes paid pricing and docs, it would be worth a second look.
