Share an HTML Report as a Link Instead of an Attachment
To share an HTML report as a link, host its finished files and send the public page URL, not the file path on your computer. Figment's HTML app hosting accepts finished browser files for this job. You sign in to upload; readers need no account. First confirm that everything in the report is suitable for public access.
This workflow fits a public research summary, a comparison report, a workshop handout, or an analysis with browser-rendered charts. It does not fit a confidential client report that needs access control. An obscure public URL is not a private document vault.
Ask for a portable report, not a screenshot
Ask your AI to return the finished HTML, styles, and any local assets. A screenshot loses working links, selectable text, and accessible headings. A preview inside an AI chat can depend on services that are absent from the exported file.
Use this prompt with the report you have already reviewed:
Package this approved report as a standalone HTML document for public hosting.
Keep the facts and sources unchanged. Do not add new findings.
Use readable headings, a short summary, and named source links.
Put a text table next to each chart so the values remain accessible.
Do not call an AI API, require a login, or load private data.
List every image, stylesheet, script, and external dependency.
Add print styles. Do not publish or upload anything yet.
Return the finished file and a checklist of what I must verify.
The purpose of this prompt is to produce an inspectable artifact. It does not connect the chat to a hosting account. If the AI returns application source that needs a build step, ask for the built browser output. The plain-file publication guide explains the difference between source and deployable files.
Remove private data from the files, not just the screen
A collapsed section, hidden table row, or JavaScript variable can still contain the original data. Removing a name from the visible chart does not remove it from an embedded dataset. Review the full HTML, scripts, and attached files before uploading them.
For a fictional conference report, use this release sheet:
| Item | Safe public version | Reason to stop |
|---|---|---|
| Attendance | Approved totals by session | An attendee email list is embedded |
| Quotes | Approved quotations with permission | Private feedback appears in comments |
| Charts | Published data and clear units | A chart reads a private spreadsheet |
| Sources | Working public references | Links contain access tokens |
| Downloads | An approved summary file | The original private workbook is included |
These are example checks, not a report we have published. For sensitive data, use an authenticated document service or remove that data entirely. Do not ask a hosting provider to make a secret safe after you have shipped it in public files.
Publish and test as a reader
- Open Figment's HTML upload and sign in with Google.
- Upload your files or folder with
index.htmlat its root. Do not upload a ZIP or framework source. - Check the unlisted preview. Uploading does not publish the report.
- Approve that exact version to publish, then copy its public URL.
The limits are 100 files, 2 MiB per file, and 10 MiB total. Keep scripts and assets local; external CDN scripts and service workers are not supported. Browser API calls need an allowed HTTPS origin and a service that permits CORS. Server code, database hosting, and private API keys are not supported. Uploading requires no AI call. Optional AI editing is paid, and storage and hosting limits apply.
App pages use noindex and do not support custom domains. Use this path for a report you share directly, not a website that must appear in Google. Preview links are unlisted, not confidential. Keep the original files so you can correct a mistake without asking the AI to reconstruct the report from memory.
Open the resulting public link in a separate browser where you are not signed in. Read the summary, open each source, and inspect the chart labels. Try a phone-width window. A report is not ready if a wide table hides the conclusion or a chart depends on a missing file.
If the report has filters, test a filter with no matching results. Confirm that its totals remain correct after you reset it. Publish a report version and its data date together so the reader knows which numbers they are seeing. Hosting a report does not make its underlying dataset current.
Check the printed copy too
Some readers will save the report as a PDF. MDN's printing guide explains how print-specific styles can change the printed layout. Check the actual print preview for cut-off tables, empty chart areas, and text that disappears on a white background.
A Print button can call the browser's print method. It opens the print dialog; it is not proof that the output is well formatted. Use the reader's normal browser print command if the page has no button.
The final deliverable is simple: one public reader link, a clear report date, verified source links, and a clean print preview. Keep any private management link separate. A reader needs the report, not permission to replace it.
Sources reviewed 2026-09-23: MDN Printing and Window.print, linked above. The release sheet and prompt are editorial examples, not measured customer results.
