Share a Rendered HTML Page Instead of a Download

If you've ever exported a report, a design mockup, or a dashboard as a static HTML file, you know the usual flow: share it, and whoever opens the link gets a download prompt instead of the page itself. Today that changes — Filewisp shares can render a self-contained .html file directly, so the link opens straight into the page.

What you can do now

• Toggle "Serve as HTML" on any share of a .html file — at creation or any time after, from the shares table
• The link renders the file inline, full-bleed, instead of showing Filewisp's usual preview/download card
• Password, expiration, and max views still apply exactly as before — this only changes how the content is presented once access is already granted

It's a small switch, but it's the difference between "here's a file, download it to look at it" and "here's the thing itself."

How it's isolated

Rendering someone else's HTML on your domain is a real attack surface, so the viewer runs in a sandboxed iframe with the strictest settings that still let a static page work: scripts are allowed (so charts and interactivity in your export still run), but the frame gets no access to cookies, storage, or the parent page, and it can't open popups, submit forms, or trigger downloads on its own. The share's access rules — password, expiration, view limits — are enforced before any of that content is ever fetched.

Why this matters

Reports, dashboards, and design exports are usually meant to be looked at, not downloaded. Now the share link does exactly that — paste it, and whoever's on the other end sees the page, not a file picker.