About DocViewer.One

What it is

DocViewer.One is a small web app that takes HTML files you've stored in Google Drive and renders them as actual web pages, not source code. You get a shareable link that anyone can open in a browser — no Google account required, no Drive access needed on their end. Just a URL that shows the page.

Why it exists

Google Drive is a reasonable place to store documents. But if you've ever tried to share an HTML file from Drive, you know the problem: the recipient sees raw markup. Angle brackets, style declarations, the whole unstyled mess. Drive previews HTML as code, not as a page.

If your document is an HTML report, a design comp, a proposal, or anything that relies on CSS to look the way it's supposed to look — there was no clean way to share it from Drive without hosting it somewhere else entirely. DocViewer.One fills that gap. Keep your files in Drive where they already live, and get a shareable rendered view without any extra infrastructure.

Who built it

I'm Subashis, a developer based in India. DocViewer.One is a solo indie project — no investors, no team, no product-market-fit deck. Just a tool I needed, built carefully enough that other people could use it too.

I built it because I had the problem myself and couldn't find a clean solution. The workarounds were all worse than the original problem. So I spent the time to do it right: proper OAuth scopes (read-only, nothing more), encrypted token storage, fast rendering, and a sharing flow that doesn't require the person on the other end to log in to anything.

The tech

DocViewer.One is built with Next.js on the frontend and backend, with authentication via NextAuth and the Google OAuth 2.0 flow. File access uses the Google Drive API with the drive.file scope — we only access files you explicitly select via the Google Picker or upload directly. DocViewer.One cannot see the rest of your Drive.

OAuth tokens are stored encrypted (AES-256-GCM) in a PostgreSQL database. HTML files are never stored on our servers; they're fetched from Drive at render time and cached briefly at the CDN edge to reduce latency on repeat views. Your files stay in Drive — DocViewer.One is a rendering layer, not a second storage system.

Feedback welcome

DocViewer.One is still early. If something isn't working the way you expect, if a feature would make it meaningfully more useful for your use case, or if you've found a bug — I want to hear it. This is a real product used by real people, and I read every message.

Reach me at the contact page or directly at support-docviewer-one@googlegroups.com.