BULK PAGE CLONER FOR CONFLUENCE
.png)
Limits
The hard numbers, and the arithmetic behind them.
Limits
Two numbers bound a single clone, and one that belongs to Confluence rather than the app.
| Limit | Value | Counted how |
|---|---|---|
| Copies per clone | 25 | Per run. The slider stops at 25, and typing a larger number into the box snaps back to it. |
| Source pages per clone | 1 | Every copy comes from the one page you picked in Step 1. To clone from a second template, run the flow again. |
| Confluence storage | Your plan’s quota | Not the app’s limit and not visible to it — see below. |
Cloning costs storage, because attachments are copied too
A copy is a real duplicate, not a link to the original. Attachments come with it, which is what makes embedded video and images render on the copy instead of breaking — but it means the files are written again for every page you create. Clone a page carrying a 50 MB video 25 times and Confluence stores roughly 1.25 GB, not 50 MB.
Confluence enforces its own quota, and the app cannot see it. If your site is at its storage limit, Confluence blocks new content with a banner like “You can’t edit or create new content in Confluence until you upgrade for more storage or delete files”, and a clone will fail for that reason rather than anything the app did. Free space in Confluence or upgrade the plan, then run the clone again. A page with no attachments costs almost nothing to duplicate, so this only bites on media-heavy templates.
There is no per-file size limit in the app itself. Copying is performed by Confluence’s own server-side copy operation, so whatever the source page can hold, a copy can hold too.