Remote Content
Remote Content embeds another web page inside a Confluence page. Give the macro an address and it renders that target in a frame sized and positioned the way you choose: a live dashboard, a PDF, an image, a video, a status page, or an internal tool.
The app has no backend. It makes no network calls of its own, stores nothing outside your Confluence page, and requests no Confluence API permissions. Your browser loads the embedded site directly, exactly as it would if you opened the address yourself.
Start here
- Edit a Confluence page and insert the Remote Content macro.
- Enter the address of the page you want to embed.
- Adjust width, height, margins, and alignment if the defaults do not suit.
- Use the Preview tab to check the result, then select Save and publish the page.
The full walkthrough is in Getting started.
What the app provides
| Capability | Details |
|---|---|
| Embed any address | Any http:// or https:// URL. A scheme-less address is treated as https. |
| Sizing | Width and height in pixels or any CSS unit, defaulting to full column width and 400 pixels. |
| Placement | Left and top margins, negative values included, and left, center, or right alignment. |
| Live preview | A Preview tab in the settings panel renders the embed with your current values before you save. |
| Refusal handling | A site that forbids framing gets an explanation instead of a blank box. |
| Open in new tab | A control on every embed opens the target directly, whether or not the frame loaded. |
| Anonymous and unlicensed viewing | Supported for readers when the Confluence page itself is accessible. |
Important limits
Many sites refuse to be displayed inside another page. That is the site’s decision, not a limitation of this app, and no app can override it — see Security and limitations.
Embedding does not bypass authentication either. A target that requires a login shows its own sign-in screen, or refuses to load, depending on how it is configured.
Documentation
- Getting started: insert the macro and embed your first page.
- Macro settings: the address, sizing, margins, alignment, and scrollbars.
- Compatibility and migration: what changed when the app moved to Forge.
- Security and limitations: what the app can reach, and what it deliberately cannot.
- Privacy policy: what data the app handles, and your GDPR and California rights.