How to copy a space in Confluence Cloud

Checked against Atlassian's documentation on 2 November 2026. Written by the maker of Spacewright, a Confluence app. We say where the app helps and where it does not.

Short answer: Confluence Cloud has no built-in "Copy space" action. The request for one, CONFCLOUD-3191, has been open since 2005 and has 883 votes. The closest native route is to create a new space and then duplicate the source space's page tree into it in one go. Blog posts, space permissions and the space's page templates do not come along that way.

Confluence Data Center has had a built-in Copy Space feature since version 8.3. If you read instructions that mention Space tools → Overview → Copy Space, they are for Data Center, not Cloud. Moved from Data Center? See what Copy Space did and what replaces it in Cloud.

Option 1: duplicate the page tree into a new space (native, any plan)

  1. Create the new space (Create → Space) with its name and key. On the Premium plan you can copy the source space's access while creating it; see copying space permissions.
  2. In the source space, open the top page of the tree you want, usually the space's home page. You cannot do this while editing.
  3. Open More actions (•••) → Duplicate.
  4. Choose the new space as the destination, and the page in it that the copy should sit under.
  5. Tick Include children and select Next.
  6. Name the new items. Confluence needs unique titles within a space, and you can rename items in bulk. For each item you can also choose whether its restrictions and labels are copied.
  7. Select Duplicate.

You need permission to add pages in both spaces. Atlassian's knowledge base describes the same route for copying a whole space, followed by tidying the page order in the new space.

What comes across, and what does not

ItemWith Duplicate + Include children
Pages and their children, in orderYes
Attachments on those pagesYes
Labels, page restrictionsYes, if you keep them ticked for each item
Comments, page history, watchersNo (Atlassian's article says so)
Blog postsNo. They are not part of the page tree.
Space permissions, description, logo, sidebarNo. These belong to the space, not to pages.
The space's own page templatesNo. Recreate them, or use global templates instead.
Links between the copied pagesReported to point at the copies when the whole tree is duplicated in one operation. Pages copied one at a time keep pointing at the originals. Check after copying.

The link behaviour above comes from users' reports on Atlassian Community, not from Atlassian's documentation, which does not describe it. If your space has several top-level pages, each separate duplicate is its own operation, so links between those trees can still point at the source. The links guide has a ten-minute check.

Option 2: export and import (a workaround, not a copy feature)

Atlassian's knowledge base article How to copy or rename a space in Confluence (updated 17 August 2026) describes exporting a space, editing its key inside the export files, and importing it again. Keep in mind:

Copying to a different Confluence site

That is a different job. Atlassian Administration has its own tools for transferring spaces between Cloud sites, with link fixing for a limited time afterwards. They are not meant for making a second copy on the same site.

Option 3: a Marketplace app

Several apps on the Atlassian Marketplace copy whole spaces or save spaces as templates. Whichever you try, test it on a small space first and check:

Where Spacewright helps

Spacewright is our app for Confluence Cloud. It copies a whole space on the same site in one job: pages and folders in tree order (including folders at the top level of the space, next to the home page), blog posts, attachments, labels, content properties and the space's page templates, and optionally page restrictions and space permissions. Links and macro settings that pointed at the source space are switched to the new space. A dry run shows the numbers before you start, and a report page in the new space gives the totals and lists what it could not copy, what it skipped, what failed, and every link it could not switch.

It does not copy comments, page history, whiteboards, databases, smart links in the page tree, or the space's logo, description and sidebar. The dry run and the report list each whiteboard, database and smart link under Not copied, with where it is in the source space, including those at the top level; the pages inside them are copied. Spacewright finds top-level content through Confluence search, which can miss items created moments before a copy. The full list is in Limits and known gaps; how a copy works is in Copying a space.

Sources