Getting started

Install the app

Install Remote Content from the Atlassian Marketplace onto your Confluence site, as a site administrator. Nothing needs configuring afterwards: the app has no settings of its own, no account to create, and no service to connect.

Embed your first page

Edit a Confluence page.
Insert the Remote Content macro.
The settings panel opens on its General tab. Enter the address in Remote content URL.
Open the Preview tab to see the embed as readers will.
Select Save, then publish or update the page.

The address may be written with or without a scheme. example.com/report, https://example.com/report, and //example.com/report all resolve to the same https address. Only http:// and https:// are accepted; anything else is rejected with an inline error.

Adjust the size

A new macro fills the width of its Confluence column and stands 400 pixels tall. Both are settings:

Width and Height take a plain number of pixels, or a value with a unit such as 100%, 50vh, or 30rem.
Margin left and Margin top shift the frame within its space. Negative values are allowed.
Horizontal alignment places a frame narrower than the column to the left, center, or right.

Macro settings describes each one in full.

Check the result

Preview the published page. An embed that loaded shows the target site; hover it and an Open in new tab button appears in its top-right corner.

If the target refuses to be framed, the macro shows a message saying so, with the same button. This is the normal outcome for a great many sites, and it is the site’s own policy at work rather than a fault in the macro or the address.

Common first-embed problems

Symptom	Likely cause
“This site refuses to be embedded”	The target sets `X-Frame-Options` or a `frame-ancestors` policy that excludes Confluence. Nothing on the Confluence side can change this. Link to the site instead, or embed a page the owner permits.
“Only http:// and https:// addresses can be embedded”	The address carries a scheme the app rejects, such as `ftp:`, `file:`, or `javascript:`.
“That doesn’t look like a valid web address”	The address is malformed, usually a typo or a missing host.
The frame is there but shows a login screen	The target requires authentication. The embed is an ordinary browser request; sign in there as you normally would, if the site permits it inside a frame.
The embed is much shorter than expected	No height was set on a macro migrated from the older version. Set one; see Compatibility and migration.
The frame is briefly blank, then shows the refusal message	The target took longer than five seconds to respond. Reload the page; if it loads, the site was simply slow.