How to Create a Perfect Snapshot for a Date in the Past With Attachments for Confluence


It is a feeling every quality assurance lead or project manager is familiar. An auditor asks for the complete v1.2 documentation from a release that you handled 3 months ago. You go to your Confluence space to find what you are looking for. Unfortunately, the pages have been updated a hundred times since then, and you never created a formal, frozen record of that milestone.

Of course, you try Confluence’s native ‘’Version History’’ as an option. But, there is a few problems about it:

It’s a Mess: Page history is a log of every single save, not a clean milestone.

Attachments: Finding the right page version is hard enough, but finding the specific version of the PDF or Word documents attached to it on that exact date? That’s Confluence blind spot.

It’s Not Just a Single Page: You aren’t always looking for an old version of just one page. Often, you need to retrieve specific versions for an entire set of documents at once—a capability Confluence simply doesn’t have.


Why Confluence’s Native Version History Isn’t Enough?

Native Confluence is designed for real-time collaboration, not for formal, point-in-time record-keeping. When an auditor asks for an accurate historical record, they don’t want a long list of page edits; they want a single, provable, and complete artifact.

A page’s history and an attachment’s history are not truly linked. You may find the v2.0 page, but it might be pointing to the v3.0 attachment, making your “snapshot” inaccurate and non-compliant.

You need a Confluence document snapshot, but it feels like the moment is lost forever. You can’t go back in time. Or, can you?

How Baselines for Confluence Solves These Problems?

This is precisely why we built Baselines for Confluence, which solves both of these critical problems with two powerful creation methods.

Baselines for Confluence is a great Atlassian Marketplace app to create snapshots of your pages and attachments. With Baselines, you can create snapshots based on a specific date and time or by selecting page versions. The created baseline set allows you to easily access document versions from that time.

To fix the “unlinked attachment” issue, the app offers a “by Selecting Individual Item Versions” option. This lets you hand-pick a specific page version and automatically bundles the attachments that were saved at the same time as that page, ensuring a perfectly synchronized record.

To solve the “I can’t go back in time” problem, the app introduces the “Based on a Date” option, which acts as your project’s time machine.

Creating a Snapshot for a Past Date

Let’s say you need to capture that v1.2 release months ago. Here are the steps you need to follow:

That’s it.

Capturing Pages and Attachments

In the background, Baselines for Confluence gets to work. It queries your Confluence space and assembles a complete, perfect snapshot of every document as it existed at that exact moment.

This is the critical part:

The app then bundles all these version-specific links into a single, formal, and named “Baseline.” You now have a verifiable artifact, created today, that perfectly represents your project’s state from months ago.

From Audit-Anxiety to Audit-Ready

This feature moves beyond a simple convenience; it’s a lifeline for Confluence version control and compliance.

The app also helps you manage your snapshots. You can compare any two baselines to instantly see what’s Added, Removed, or Changed, and even view page differences side-by-side with a single click.

You have full control to delete old baselines when they’re no longer needed. Deleting a baseline is safe. It only removes the snapshot, never your actual Confluence pages.

With Baselines for Confluence, you have the power to go back and create a perfect, complete document snapshot, including all attachments—for any date, anytime you need it. Visit Baselines for Confluence’s Atlassian Marketplace page to learn more, or its documentation page to see how it works.