Skip to content
Docs
Sign in

Proofs and Files

Every proof is kept in Files. Send a PDF from Files for approval, see each version's approval there, and choose what a new version does.

Approvals keeps its PDFs in Files, your team's file library. Every proof you upload is also a file version there, and any PDF already in Files can be sent for approval without uploading it again. Files shows which version of a file was approved, by whom and when, and when a newer version of a file arrives, both apps say so and ask what to do with it.

Open Approvals

Every upload is kept in Files#

When you upload an artwork's first version, Files gets a new file named after the artwork, for example "Carton 200.pdf", in a folder called Approvals. Each later version you upload becomes the next version of that same file, so Files holds the whole history of the artwork.

  • The proof shows exactly the bytes in Files. They are stored once, never copied, and a PDF that is already in Files costs no extra storage (see Storage).
  • You can rename or move the file and the Approvals folder in Files. The next upload still goes to the artwork's file, wherever it is. If the file is in the trash, the upload starts a new file in Approvals.
  • In Files, these versions carry the Approvals badge. The file's Activity lists each proof round ("Used in an app: Approvals: Carton 200, proof round 2"), and Sent for proof once reviewers are emailed its link. Its Details and Versions show each version's approval (see ).
  • A row's File v5 opens the file in Files, and so does Open in Files in the row's ⋯ menu.
  • A proof shared from the 1-up editor of an imposition job keeps its own copy of the print-ready PDF instead: it is a proof of those exact bytes, not a new version in Files, and it doesn't count toward your storage.

Choose a PDF from Files#

In the upload dialog (Upload artwork, or New version in a row's ⋯ menu), choose Choose from Files instead of dropping a PDF.

  1. Find the PDF in the Files window: browse the folders or search, then choose Select. Only PDFs can be picked, and only once Files has finished reading them.
  2. For a new artwork, Artwork name starts as the file name.
  3. Choose Add artwork (or Add version for a new version of an artwork).

The version uses the file's current version in Files, with nothing uploaded, and the artwork's history lists it as v3 added from Files. If another artwork already proofs that file, Upload artwork adds the version to that artwork rather than starting a second one, and the message names that artwork. If Files already checked the file version with your team's default profile, the new version shows that report instead of checking the same PDF again.

You can also start from Files: Send for proof on a PDF there does the same (see Files).

A one- or two-page PDF with a dieline in Files also gets a 3D proof on its links, with a two-page PDF's page 2 printed inside (see 3D proofs in approvals).

When a newer version is in Files#

Someone may add a corrected PDF straight into Files, for example by dropping it onto the file. The artwork's row on the Approvals page then shows v6 available under its version (with the file's own number). Nothing changes by itself: the proof your reviewers see stays on the version they were sent.

To send it, choose v6 available, or Send v6 for approval in the row's ⋯ menu.

  1. Reviewer emails starts with the reviewers of the current version. Remove or add addresses; leave it empty to share the new version later from Share. Only the addresses in this box are emailed.
  2. Add a Message if you like, and choose Send to reviewers (or Add the version without reviewers).

The PDF becomes the artwork's next version and the older versions lock, as after any upload (see Artwork versions). The reviewers get a personal link to the new version by email. If the current version has a staged approval, sending the new version to its reviewers starts that approval over at its first stage: only the first stage is emailed now, and the others follow as each stage approves (see Staged approvals). An address you add that was not part of the staged approval joins its first stage.

Add the version without reviewers emails nobody, now or later, and a staged approval does not restart: the new version waits on its row until you share it. Every case is listed in Artwork versions.

Signed-in team members see the same news on the proof page, in a strip under the header, with a button that opens this dialog. Reviewers never see it.

A file's approvals in Files#

Select a PDF in Files to see where it stands in Approvals, without leaving Files.

  • Details has an Approvals list: every version of the file that was sent for approval, newest first, with the file's version number, its status, who decided and when, and the artwork it belongs to. Open shows that artwork's row on the Approvals page, where the version number opens every version with its approvers and its proof (see Artwork versions).
  • Versions shows the same line on each version, so the history reads as "v1 Approved 12 Mar by Ana Ruiz" and "v2 Pending". The current version says Not sent for approval when an older version is the one in approval.
A file's Approvals list in Files with one approved version and a newer version that was not sent
A file's Details in Files: v1 approved, and v2 not sent for approval yet
Status What it means
Approved The version was approved, with the approvers' names and the time. A staged approval reads Approved once its last stage approved.
Rejected A reviewer asked for changes, with their name and the time.
Pending The version is out for approval: how many reviewers it is waiting for, or the stage that is deciding ("Stage 2 of 3: Customer").
Not sent The version is in Approvals, but nobody was asked to approve it yet.
Replaced A newer version was sent before this one was approved. It can no longer be approved.

An approval belongs to one version of the file. When v1 was approved and you add v2, v1 still reads Approved (that is the file your customer signed off), and v2 has no approval until you send it.

One file, one approval per version#

A file has one artwork in Approvals, and each version you send is one approval of that artwork. A version can have several links (Simple, Advanced, a 3D proof) and one staged approval; its status is read across all of them, exactly as on the Approvals page. Sending a file that an artwork already proofs always adds to that artwork, so a second approval of the same file does not start by accident. If two artworks do proof the same file (for example through the API), Files lists both, each under its artwork's name.

When a file in approval gets a new version#

Adding a version in Files changes nothing in Approvals by itself: reviewers can still approve the old version while the new one sits in Files. So when you add a version to a file whose earlier version is out for approval or was approved, by uploading it, dropping it on the file or restoring an older version, Files asks straight away: v2 has not been approved.

The question Files asks when a new version is added to a file that was approved
The question Files asks after v2 is added to a file whose v1 was approved

The dialog says where the earlier version stands (approved by whom and when, rejected, or out for approval and at which stage) and what sending does.

  • Send v2 for approval makes it the artwork's next version. The earlier version locks: it can no longer be approved, and its decisions stay in the history. With Ask the same reviewers again ticked, each reviewer of the earlier version gets a personal link to the new one by email, and a staged approval starts over at its first stage with the same stages and approvers. Untick it to add the version without emailing anyone, and share it from Approvals when you are ready.
  • Choose other reviewers… opens the Approvals page on Send v2 for approval, where you can edit the list and add a message.
  • Not now leaves everything as it is. The earlier version keeps its approval or stays out for approval. The file's Approvals list and the artwork's row both keep saying that v2 has not been sent, each with a button to send it later.

Files does not ask when the earlier version was never sent to anyone, or when the content you add is the content already in approval (restoring the approved version, for example). After an upload of many files, one file in approval brings up the question; with several, a notice points you to the Approvals page, where each row says v2 available.

Send for proof on a file that is already in approval asks the same question first, so previous reviewers are never emailed without you choosing it.

Two version numbers#

An artwork's versions and its file's versions are numbered separately. A row can read v2 with File v5 under it: the second version sent for approval was made from version 5 of the file. Versions made in Files but never sent don't count as approval versions, and sending the same file version twice in a row adds nothing (two clicks at once add one version).

Deleting and the trash#

Approval versions keep the file version they show. As long as a proof uses it:

  • Files won't delete that version, and a trashed file that a proof still uses is kept in the trash rather than purged (see Versions);
  • the file's Where used lists the artwork, for example "Approvals: Carton 200, proof round 2".

The other way round, removing an artwork or a version from Approvals never deletes anything in Files: only the PDFs Approvals keeps itself, such as a proof shared from the 1-up editor, are removed with it.

In the API#

Uploads through POST versions/ are kept in Files the same way; files_folder picks the folder for an artwork's first file. POST versions/from-file/ sends a version from Files, and every version reads its file_id, file_version_number and file_latest_version_number. GET files/{id}/approvals/ answers what the Files panel shows: every version of a file that was sent, with its status, and the newer version waiting. See Approvals API and Approvals API.

Last updated Nov. 17, 2026