Export Lapis stories

Modified on Sun, 8 Mar at 9:19 PM

Quick Links


Export as iframe

Exporting your story as an iframe lets you embed Lapis story directly into any external website such as a news article, blog, or web page, so readers can interact with your Lapis story without leaving your site.

Before you begin: Your story must be published before you can export it as an iframe. If your story is unpublished, publish it first before following the steps below.


Access the iframe export panel

  1. Open your story in the story builder.

  2. Click the settings icon (cog icon) beside the story title.

  3. Click Export.

  4. Select Export as iframe.

An iframe code snippet will be generated and displayed in the panel, ready for you to copy.


Copy the iframe code

  • Click Copy to clipboard to copy the iframe embed code in one click. The generated iframe code includes width="100%" by default, along with allowfullscreen and loading="lazy" attributes for the best viewing experience.
  • Copy the embed link. In addition to the iframe code, you can also copy an embed link from the same panel. This is useful for pasting your story into compatible platforms that accept embed URLs directly.


Embed your story on an external website

  1. On your external website, add an iframe embed element to your page.

  2. Paste the iframe embed code you copied from Lapis. Your Lapis story will be displayed responsively across devices — desktop, tablet, and mobile. 


Keeping your embed up to date

The iframe always reflects the latest published version of your story. If you make changes to your story after embedding it, republish the story and your embed will automatically update — no need to replace the embed code.


If you open the Export panel after making changes to a published story, you will see an alert letting you know that the story has unpublished changes. Republish your story first to ensure the embed reflects your latest edits.


Visibility and access

Your story's visibility settings are respected in the embed. You can export as an iframe regardless of whether your story is set to public, unlisted, or private. Your embed will honour the original access settings.


Export as HTML

Exporting your story as HTML lets you download a self-contained version of your story that you can host on your own server or web infrastructure. The exported file preserves your story's layout and interactive charts, exactly as they appear on Lapis.


Before you begin: Your story must be published before you can export it as HTML. If your story is unpublished, publish it first before following the steps below.


Access the HTML export panel

  1. Open your story in the story builder.
  2. Click the settings icon (cog icon) beside the story title.
  3. Click Export.
  4. Select Export as HTML.


Download the HTML file

Follow the instructions in the export panel to download your HTML file. Click Download HTML to download your story. The exported file will look exactly the same as your story on Lapis.


What's included in the HTML export

The exported HTML file preserves both static and interactive charts from your story. Interactive embeds remain fully interactive in the exported file — readers can hover, filter, and explore the data just as they would on Lapis. However, charts created on Lapis will lose interactivity.

Notes:

  • Fonts should appear as intended, but font files are not included in the folder.
  • Maps and interactive blocks that rely on external APIs may require reconfiguration.
  • Third-party embeds require internet access and may not work offline.


Viewing Instructions

  • For hosting: Upload the folder to any web server or CDN. It will also work in any subdirectory.
  • For local viewing: Use a simple local server (e.g., npx serve, XAMPP, or VS Code Live Server)

Export as PDF

Coming soon.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article