How to copy a Confluence space template to another space
In Confluence Cloud, you can recreate a custom page template in another space by copying its body into a new template. A global template is a better fit when the whole site should use one shared version. For separate copies in several spaces, preview the destination and name conflicts before you copy.
Copy one custom page template by hand
Use the source and destination space settings. You need permission to edit templates in both spaces. Atlassian documents how to create a space template and describes the manual copy workaround in its issue tracker.
- In the source space, open Space settings → Look and feel → Templates. Edit the template and copy its body.
- In the destination space, open the same menu and select Create new template. Give it a name, paste the body and save. Check the description and labels separately.
- Create a test page from the new template in the destination. Check that its variables prompt for the right values and that its links and macros point to the right content.
Use a global template when every space needs the same version
Ask a Confluence administrator to create a global template if the template should appear in the site-wide gallery, such as a shared incident review. In Confluence administration, open Settings → Configuration → Global templates and blueprints and select Add global content template. Paste or recreate the body, check the variables and save. Keep separate space templates when teams need different wording or when the template should be available only in specific spaces. Atlassian’s global template instructions cover the administrator path.
Preview the copy in a test space
Template Porter copies custom page templates between spaces on the same Confluence Cloud site. Start with one template and a test space where you have administrator permission.
- In Template Porter, open Copy, choose the source space and template, then select your test space under Copy to.
- Choose Skip to keep a template that already has the same name, or Rename to keep both. Select Preview copy and check the action shown for the test space.
- Review warnings for people, page links and attachments before confirming. Mentions and links may still refer to the source, and attachment files do not come with the copy. Check any macro that names the source space and update references where needed.
- If the preview shows Skip, choose Rename or pick a test space without a matching template. Confirm a Create or Rename action, then create a page from the copied template. Once it works, preview the run for your other destinations.
Template Porter supports custom page templates. Atlassian Blueprint templates fall outside its copy workflow.
Atesen Software publishes this guide and makes Template Porter. See Template Porter on Atlassian Marketplace for the current plans and installation.
Questions people ask
Can you copy a space template to another space in Confluence Cloud?
By hand, yes. Open the template in the source space, copy its body, and paste it into a new template in the destination space. Atlassian describes this manual workaround in its issue tracker under CONFCLOUD-79178.
Where are space templates in Confluence Cloud?
In the space, open Space settings, then Look and feel, then Templates. You need permission to edit templates in both the source and the destination space.
When should I use a global template instead?
When the whole site should use one shared version, such as a shared incident review. A Confluence administrator adds it under Settings, Configuration, Global templates and blueprints. Keep separate space templates when teams need different wording or when the template should be available only in specific spaces.
What should I check after copying a template?
Create a test page from the new template. Check that its variables prompt for the right values and that its links and macros point to the right content. The description and labels are checked separately because they are not part of the body.
Does Template Porter copy attachments and blueprints?
No. Attachment files do not come with the copy, and mentions and links may still refer to the source space. Template Porter supports custom page templates; Atlassian Blueprint templates fall outside its copy workflow.