Will my interactive plots work?

Yes, as long as they run in the browser. Plotly, Leaflet, Observable JS and htmlwidgets all work, because their JavaScript ships inside the rendered output.

What about Shiny documents?

Those need a live R or Python process, so they can't run on static hosting. Render to static output instead, or host the Shiny app on a server.

Can I publish a single report rather than a whole site?

Yes. Upload the rendered HTML together with its _files folder, keeping them side by side so the plots load.

Can I keep it private?

Yes. Set a password at publish time, and the report stays out of search results as well.

How do I share an update?

Re-render and publish to the same address. Everyone with the link sees the new version, and the old one is kept if you need to compare.

Host your Quarto site or report at your own address

quarto render turns notebooks and Markdown into a site. Drop _site in and your analysis is live over HTTPS, charts and all.

You can host:

index.html/assetsfolder.zip

Drop your _site folder here

Any other file works too — up to 25.0 MB, or 100.0 MB for a whole site

Choose a fileor drag it anywhere in this box

Free to use, live at your-name.99helpers.site in about ten seconds.

Why the rendered output has nowhere to go

Quarto renders notebooks, R Markdown and plain Markdown into a proper website: interactive plots, cross-references, a table of contents, the lot. Then comes the awkward part, which every analyst knows — the output is an HTML file with a folder of assets beside it, and email does not handle that gracefully.

What a Quarto build gives you

A _site folder with every page rendered to HTML
A _files folder per document, holding plots, data and JavaScript libraries
Interactive output from Plotly, Observable, Leaflet and friends, working in the browser
A search index, if you've enabled site search

Build it, then upload it

Build command: quarto render
Folder to upload: _site/
Base path: Quarto writes relative paths between pages and their resource folders, so the rendered site works at any address.

An HTML report is never one file

Send the .html on its own and the plots vanish, because the _files folder beside it never made it into the email.

Shared drives mangle it

Uploading a rendered report to a drive usually means colleagues download it, open it locally, and hit the same missing-assets problem.

Stakeholders won't run code

The people who need the analysis want a link that opens. They are not going to clone a repository and render it.

Publishing a Quarto site

1
Render the project
Run quarto render. For a website or book project, everything lands in _site — HTML pages plus the per-document _files folders they depend on.
2
Upload the whole folder
Drag _site in, keeping the structure intact, so each page keeps the assets it references. Choose an address and it's live over HTTPS.
3
Send the link
Anyone can open it in a browser, with plots and interactivity working. Re-render and publish to the same address when the numbers change.

Worth knowing

For a single document, quarto render report.qmd gives you report.html and report_files — upload both together as a folder, with the HTML renamed to index.html if you want it at the root.
self-contained: true embeds assets into one HTML file, which is handy for a single report but produces a much larger file.
Anything that needs a live R or Python session — Shiny documents, server-side Observable — won't run on static hosting. Rendered output works fine.
If the analysis is confidential, set a password when you publish so only the people you send it to can open it.
Plot-heavy projects can produce hundreds of files; the limit is 500 files and 100 MB per site.

Questions

Will my interactive plots work?: Yes, as long as they run in the browser. Plotly, Leaflet, Observable JS and htmlwidgets all work, because their JavaScript ships inside the rendered output.
What about Shiny documents?: Those need a live R or Python process, so they can't run on static hosting. Render to static output instead, or host the Shiny app on a server.
Can I publish a single report rather than a whole site?: Yes. Upload the rendered HTML together with its _files folder, keeping them side by side so the plots load.
Can I keep it private?: Yes. Set a password at publish time, and the report stays out of search results as well.
How do I share an update?: Re-render and publish to the same address. Everyone with the link sees the new version, and the old one is kept if you need to compare.

Publish the Quarto build you already have

Drop the folder in at the top of this page and see the link for yourself. You only make an account once it's ready to go live.

Back to the top Every generator we cover

Hosting sites from other tools

Hosting guides by file type

Every site gets its own address on 99helpers.site — see static site hosting for every generator, how website hosting works here or free file hosting for any file type.