Charts an AI built for you are real, running JavaScript. Publishing them as a page keeps them interactive instead of flattening them into a screenshot.
Charts and tooltips keep working — publish it interactive, not as a screenshot.
Ask an AI assistant to "turn this CSV into a dashboard" and you get back a single HTML file with a charting library, your data inlined, and some tooltips. It works in the preview panel. Then you need to show it in Monday’s meeting, and the usual fallback is a screenshot — which throws away every hover, filter, and drill-down that made it a dashboard rather than a picture of one. Publishing the file as a page keeps the interactivity, and gives you something to paste into a calendar invite so people can look before the meeting instead of during it.
An operations lead exports last quarter’s ticket data and asks Claude for a dashboard: volume over time, a breakdown by category, and median resolution time, with the data embedded so the file stands alone. The result is about 400 lines of HTML with a charting library pulled from a CDN. Pasted and published, the charts render and the tooltips respond, because scripts run in the published sandbox and an external library loaded over HTTPS still loads. What does not carry over is anything reading from a local file path — a dashboard written to fetch("./data.csv") shows empty charts, because there is no sibling file next to a published single document. The fix is to ask for the data inlined in the HTML, which is worth specifying in the original prompt. Since the numbers are internal, the lead adds a password before sending the link to the team channel.
Free links last 7 days with a free account. On a paid plan every page you create stays online permanently.
See pricing