Skip to content
moorea
Two islands joined by a pale bridge over a narrow turquoise channel.

Feature

Embed the tour in your site

One iframe, three lines, no plugin. And crucially: no cookies, no persistent identifiers - the first question a legal team asks, and the one that makes an embed drag on for six weeks.

Updated August 2026

Three ways to embed

In order of simplicity. The first covers 90 % of cases.

  1. Step 01

    Copy-paste the iframe

    The tour’s Share button gives you ready-to-paste code, with the right aspect ratio and lazy loading already set.

  2. Step 02

    Paste the URL (oEmbed)

    On WordPress, Notion, Slack or any oEmbed-aware tool, just paste the tour link: the interactive preview builds itself.

  3. Step 03

    A custom HTML block

    On a hand-built site or a restrictive CMS, an HTML block with the iframe is enough. No JavaScript library to load.

  4. Step 04

    Drive it from the page

    Going further, the iframe accepts messages: open a specific scene, start rotation, listen for view changes.

The code

The three lines to paste

The tour’s Share button hands them over pre-filled. Here they are in the open, so you know exactly what you are pasting.

<iframe src="https://embed.moorea.app/YOUR-LINK" style="aspect-ratio:16/9;width:100%;border:0" loading="lazy" allowfullscreen></iframe>

Aspect ratio, not a fixed height. aspect-ratio keeps the tour readable on a phone and on a large screen alike.

loading="lazy" is not optional. Without it the iframe loads even if the visitor never scrolls to it.

allowfullscreen enables fullscreen. One line, and a thumbnail becomes a tour.

Going further

Driving the tour from your page

The iframe accepts messages, both ways. That is what links the tour to the rest of the page - a clickable map, a tab, a button.

What you can send: goToScene, goToGroup, lookAt, setAutorotate, getState.

What the tour sends back: ready, sceneChange, viewChange, hotspotClick.

The relay only accepts messages from the direct parent.

From the Pilot plan up, allowed embedding domains further restrict where the tour can be displayed.

The three classic pitfalls

A botched embed almost always fails for the same reason: weight, consent, or aspect ratio.

Weight. An iframe loaded immediately at the top of a page delays everything else. The loading="lazy" attribute - included in the share code - only loads the tour as it approaches the viewport. Before interaction, the cost is close to zero.

Consent. Most video players and competing tours set third-party cookies, which puts them under consent rules: the iframe stays greyed out until the visitor accepts. The Moorea player sets none, by design.

Aspect ratio. A tour squashed into a 200-pixel-high block appeals to nobody. The share code enforces a fluid 16:9 ratio that adapts to the available width without distorting the image.

A tour embedded in a venue’s own page, cookie-free.

Questions

Do I need a WordPress plugin?

No. Paste the tour URL into a paragraph: WordPress queries our oEmbed endpoint and builds the preview. Otherwise a custom HTML block with the iframe works everywhere.

Will the embed slow my site down?

Not when lazy-loaded, which is the supplied setting. Until the visitor scrolls to it, nothing is downloaded.

Try it on a test page

Create an account, publish a demo tour and paste its code onto a draft page of your site. Ten minutes is enough to settle the question.

Create an account