How do I export a Panel app to a single HTML file?

`panel_object.save('dashboard.html', embed=True)`. `embed=True` bakes the widget states into the file so the controls still work without a running Python process. Publish that file with one curl.

What does embed=True actually capture?

The output for each combination of widget states, up to the configured `max_states`/`max_opts`. Discrete widgets embed cleanly; a continuous slider gets sampled. A dashboard with many interacting widgets grows combinatorially, so narrow the widget set for the shared version.

What is lost compared to a served app?

Anything that runs Python on interaction — live queries, model inference, callbacks over new data. If your dashboard needs those, publish a snapshot on a schedule instead and let the routine re-run the Python.

How do I keep the dashboard current?

PATCH the same report id from a routine. The script re-runs, saves the HTML, and refreshes the report, so the URL people bookmarked shows today's numbers with yesterday's still available as a revision.

Can people comment on it?

Yes. Threads anchor to the rendered content, so 'why did the EU line drop in week 32?' sits on the chart rather than arriving as a cropped screenshot.

Share a Panel app as HTML

Panel's appeal is that a few lines of Python become a real dashboard. Its cost is that a real dashboard is a running server, and a running server is a deployment, a URL, an auth story and someone's ongoing problem.

For a large share of dashboards — the weekly number, the model evaluation, the ops summary — nobody needs live Python. They need today's version, with the controls working, at a link.

Publish it

import panel as pn

dashboard.save("dashboard.html", embed=True, max_states=16)

curl -X POST https://commareports.com/api/v1/reports \
  -H "Authorization: Bearer $COMMA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d "$(jq -n --rawfile html dashboard.html \
        '{title: "Ops dashboard — week 36", html: $html}')"

Or drag dashboard.html into the app.

The widgets keep working at the link — report HTML runs scripts inside a sandboxed iframe (allow-scripts, no allow-same-origin).

What `embed=True` can and cannot do

It precomputes the output for each combination of widget states. Discrete selectors embed well; continuous sliders get sampled; and the file grows with the product of the options, so a dashboard with five interacting widgets can become enormous. Narrow the widget set for the shared version — the shared version usually wants fewer knobs anyway.

Anything requiring Python at interaction time — a live database query, inference on new input — is not in a static export. Put the Python on a schedule instead.

Keep it current on a routine

A routine re-runs the script and PATCHes the same report, so the URL holds current numbers rather than the state of the world when someone last remembered to re-export. See scheduled HTML reports.

Limits

HTML body: 5 MB. embed=True with a wide state space passes it quickly — lower max_states, or embed fewer widgets.
Scripts run, sandboxed: allow-scripts, no allow-same-origin.
60 requests/minute per token.

Try it

Comma is free — unlimited reports, unlimited commenters, unlimited revision history.

Create your first report →