A scrollytelling piece only works while it's scrolling — the chart animates, the map pans, the text reveals as you go. Flatten it into a PDF and you've kept the words and thrown away the story. Drop the page in and get a private link that keeps the whole scroll-driven experience alive in the browser, so a client or your audience reads it the way you built it. It opens with no login on their end and stays off search, so a draft reaches the people you choose and not the open web.
Try it now
Drop a file — get a private link in seconds. No sign-up.
Drop an HTML, ZIP, PDF, PNG or JPEG file, or click to choose.
One file, or a ZIP bundle. Max 3 MB.
Up to 3 MB, link self-destructs after 7 days. Sign up free to keep links forever, password-protect them, and store more.
Export the story as a self-contained page — the HTML with its scroll logic, visuals, and fonts, zipped if they're separate — and drop it in. A private link appears in seconds; no deploy, no account, nothing to install for the reader.
Send the link. As the reader scrolls, the animations and reveals run in their browser, on a phone or a laptop, exactly as you designed — not a static export that loses the movement. It's off search, so an unpublished piece goes only to your reviewers.
Keep it yours: re-upload edits and the link holds; password a piece under embargo; set an expiry on a timed release; and on Studio serve it from your own domain so the byline reads as yours.
A PDF keeps the text and kills the story. Scrollytelling is the animation, the pacing, the reveal-as-you-scroll — none of which survives a flatten. A link keeps the page live in the browser, so the reader gets the experience you built, not a stack of static frames.
Yes, if the page is self-contained. When the scroll logic runs in the browser — the usual way these are built — miinideck serves the live page and every animation, pin, and reveal fires as the reader scrolls, on any device, with no account for the viewer.
Baked-in data and self-contained visuals work here as-is. If it must pull live figures or hide a key on each load, that part is a real backend — Vercel or Netlify — and you'd share the static front end here while the data service lives there. Third-party embeds load fine as long as they're allowed to.
Yes. The link is unguessable and no-indexed, so a draft or an embargoed piece stays off search and opens only for the people you send it to. Password it for an editor or a client, and set an expiry that matches the release date.
Free links self-destruct after 7 days; on Solo ($4.99/mo) and up they never expire, and Studio ($14.99/mo) adds a custom domain and white-label. Turn on Review and an editor pins comments to the exact section with no account, resolved in place — free on every plan.
No card to try, no sign-up to get a link. Sign up free to keep links forever, password-protect them, and store more.