Branded proof links: send clients a proof they can actually explore

Publish a 3D proof as a branded link on your own subdomain. Your customer opens it, turns the product over and signs off: no login, no attachment, no mix-ups.

A branded proof link is a single URL on your own subdomain (yourcompany.proofscene.com/P26001234) that opens the customer's job as an interactive 3D proof, in a browser, with your name on it. No attachment, no account for the client, no "which version was that". The link is the job.

The problem with emailing proofs

Every shop has lived this thread. You attach proof_v2_FINAL.pdf. The customer forwards it to their manager, who forwards it to the brand team, who forwards a screenshot back with a comment. Somewhere in there a v3 goes out to one person and not the other two. Two weeks later somebody asks which one was approved and you are reading email timestamps to find out.

Attachments create copies, and copies drift. They also strip away everything you would want the reviewer to have: the job number, the spec, the finish notes, the product itself, and any sign of whether it was even opened. The PDF arrives as a naked file in a downloads folder.

Worse, it arrives looking like nothing. A generic attachment from a generic email does not feel like a document you sign. That is a small thing, and it changes how carefully people treat it.

What a proof link changes

A link is a single source of truth. There is one address for the job. When a revision is ready, you choose the moment that address moves to it: a published link keeps showing exactly the build you published until you select Publish update. Anybody the customer forwards it to sees the same thing, at the same time, in the same state.

And because it is a web page rather than a file, it can carry the whole context of the job around the proof itself:

  • The interactive 3D product, which the reviewer can rotate, zoom and inspect under real lighting.
  • Your company name on the proof and your job number in the address, so the customer knows whose proof it is and which job.
  • A link preview card, so the link looks like a proof rather than a bare URL when it lands in email or chat.
  • A view count, so you can see whether and how often the proof has been opened before you chase.
  • An Approved status you set when the customer signs off, on the link that shows the build they reviewed.

That last point is the one production people care about most. The approved status and the build sit on the same link, which is a much better position than an inbox search. If you publish a corrected build to that link after sign-off, it shows the new one, so ask the customer to approve again.

It should look like your shop, not ours

This is the part we were opinionated about from the start. The proof link is a customer-facing surface for your business. It sits on your subdomain, the proof says it was prepared by your company, and your logo and brand color frame the link's landing and password pages. Your customer's experience is with your shop.

Practically that means:

  • Your subdomain: yourcompany.proofscene.com, with your own domain available through a white-label or self-hosted setup scoped with our team.
  • Your branding: your company name on every proof, plus your logo and brand color, set once in your account settings, so the link matches the rest of your customer communication.
  • Your job numbering: the URL path is your reference, not an opaque token. If your job is P26001234, the link is /P26001234, which means the link is readable over the phone and searchable in your own systems.

A proof link that reads like your job docket is a proof link your production office can actually use.

Creating one: drag the PDF onto the job

The workflow we wanted was the one we already did informally: take the proof PDF that prepress just produced, and put it against the job number. So that is the interaction: drop the PDF into the 3D Proof Studio, give the link your job number, publish, and the link exists.

Behind that: Proofscene reads the artwork, die line and spec from the proof sheet, builds the 3D proof, and the URL goes live when you publish. When revision three arrives, the link keeps showing the build your customer already has until you choose Publish update, so nothing changes under a reviewer mid-review.

Nothing about your prepress changes. The file you upload is the same press-ready proof you would have attached to an email. The difference is where it lands.

Access: open by default, locked when it matters

Most proofs do not need a login. Requiring your customer to create an account to look at their own job is friction that costs you approval time, and it is the single fastest way to make a proof sit unopened for three days. The default should be that the link just opens.

But some jobs genuinely are confidential: unreleased packaging, a rebrand under embargo, credentials for a client's staff, anything under NDA. For those, a proof link can carry an optional password, so the URL alone is not enough. You send the link in one message and the password however you normally handle that.

Sensible companions to that, which every Proofscene link gives you:

  • A status you control: Draft while you prepare it, Active while it is out for review, Approved once the customer signs off.
  • Archiving, which takes the link offline when the job is finished or the link went to the wrong address.
  • A custom or random code, so a confidential job does not have to carry a guessable job number.

The principle is that security is a per-job decision, not a blanket policy that slows down the ninety percent of jobs that do not need it.

What to put in the email around the link

Since the proof carries the detail, the email can be short. What works is: the job number, one sentence saying what the customer is looking at, the link, and one clear instruction about what you need from them and by when. The questions you used to answer in long emails (what the back looks like, where the foil sits) are answered by the proof itself.

One practical habit worth adopting: send the link to the person who actually signs, not only to the coordinator forwarding it. A proof link is easy to forward, which is a strength, and sending it to the signer yourself means the decision never waits on a forward.

Recording the sign-off

When the customer replies with their decision, mark the link Approved in your proof library. The link keeps showing the build they reviewed until you publish an update, its view count shows whether and how often it was opened, and the proof keeps its job reference, so "which version did they approve?" takes seconds to answer instead of an inbox search. If your proofs still live in email attachments, this is the change worth making first.

Related reading

The feature page for branded proof links has the detail, and the 3D proof viewer covers what the customer sees when they open one. For white-labeling it completely, see white-label and enterprise self-hosted. On the record-keeping side, read how to document customer sign-off and customer artwork sign-off. Related posts: turning flat PDF proofs into interactive 3D and from proof to product shot. Create a free account and send your first proof link today.

See your next proof in 3D

Create a free account, upload a proof sheet and send your customer an interactive 3D proof on your own branded link today.

Free account · No credit card · Built by print people