How to Compare Two Versions of a Proof

Every round of changes carries a risk: the designer fixes what was asked for and quietly breaks something else. Comparing the new version against the old one is the fastest way to find out.

This guide explains how to compare two proof versions in GoProof, and how to make the check part of every review round.

Why compare versions at all

Reading the new version cold means trusting your memory of the old one. People miss small changes to a price, a date, a logo or a line of legal text. A comparison removes the guesswork by showing exactly what is different, so reviewers can spend their time on the changes rather than on searching for them.

Step by step

1. Open the version history

In the proof editor, open Version history from the right-hand menu. It lists every version of the proof and its stage. You can open an older version, toggle between it and the latest, or pop a version out into its own window.

2. Choose the version to compare

Select the earlier version and use the compare action to set it against the latest. This opens GoProof's difference tool, with the two versions laid out together and scrolling and zoom kept in step, so what you inspect in one is what you see in the other.

3. Turn on Smart Compare

Enable Smart Compare to highlight the pixels that differ, in a colour you choose. Pick a colour that stands out against the artwork. Two options help further:

• Disable image colours greys out the artwork so the highlighted differences stand out.
• Show difference only hides everything that has not changed.

4. Use the side-by-side view when you need context

GoProof also has a plain side-by-side comparison of two versions. It is useful when you want to read both layouts normally rather than look for pixel changes, for example when a page has been reflowed.

5. Compare copy changes

On proofs with editable text, such as copy-edited articles, you can compare the original and current version of a story to see the text edits.

Making it a habit

• Compare every new version before approving it, even when the changes look small.
• Check two things: that every requested change was made, and that nothing else moved.
• Look at the version banner at the top of the editor. If a later version exists, it will say so, so nobody comments on an outdated file.
• Remember that comments on earlier versions are read-only. They stay visible for reference, but new feedback goes on the latest version.

When you upload the next version, the previous collaborators and roles are filled in for you, so the same reviewers are ready to look at the comparison.

Limits to know about

The difference tool is not available inside embedded apps. Open the proof in GoProof itself to use it. Smart Compare shows visual difference, so a change that does not alter how a page looks, such as hidden text, will not be highlighted.

Smarter Proofing. Faster Approvals. GoProof.

FAQs - Frequently Asked Questions