Monday
Sat's weddingShared cloud folder
This link has expired
Every shoot ends the same way: cards in pockets, files in five places, nobody sure what's missing. paperwing turns it into one tracked job — every contributor's file fingerprinted at the source, read back by our server in the cloud, and checked again on your own drive.
Contributors deliver free, no account:BrowserPhone
Everything in flight on one screen — who is still uploading, and what is waiting on you.
Drop what the job arrived as — the timeline, the contract, the email that booked it.
The couple, the date, the venue, the day's moments and the crew — filled in, for you to check.
Create it, and everyone has their own link. What comes back lands in the job — and in the bell.
Every contributor file · fingerprinted once, verified twice
01 At the source
Fingerprinted on the contributor's machine before it leaves
blake3 · per file
02 In the cloud
The cloud copy is checked against the same manifest
cloud verified
03 On your drive
Checked again locally before sign-off unlocks
/Volumes/your-drive
The promise
Not “uploaded”. Not “probably fine”. Every contributor's file matched to the fingerprint taken on their machine before it left.
What goes wrong today
Leaving the venue
With paperwing
Each contributor’s frame numbers are checked for gaps as their files arrive, while everyone still has their cards. It’s a prompt to look, not proof: frames deleted in camera leave the same gap.
2:14 am, hotel wi-fi
With paperwing
It picks up where it stopped, on the same link, for as long as the job is open. Nothing starts over.
Tuesday, the edit starts
With paperwing
Every contributor file is listed with its own fingerprint, and our server reads each one back before calling it cloud verified.
The card goes back in the camera
With paperwing
Not until the lead signs off with the files on their drive and matched. Until then, every contributor’s link says keep your cards.
If you're the one being hired
7 systems to learn6 hrs 45 min lost this week
Every studio picks its own way to get your files. You carry all of them. Here's one week of it.
Shared cloud folder
This link has expired
Their upload portal
MENU_HERO_4K.mov3.8 GB
File too large. Maximum 2 GB.
Big-file transfer + email
Transfer sent
Did you send the model release with the files?
Text thread
Uploaded everything to the drive folder 👍
Did you get them?
Agency's own uploader
Upload complete ✓
Cards handed over at the venue
card 3 — in Theo's
jacket??
Phone to phone
can u just send the best ones over text 🙏
Sending 38 now
Same week, one list. Every studio's job in one place, and you can see where your files got to without asking anyone.
What came off the card, or the edit you spent a week on. No per-file cap, no re-exporting at 1am to fit someone's portal, and a dropped connection carries on where it stopped.
The release, the invoice, the mileage log travel with the job instead of an email thread nobody can find in March.
Every job says it in the same words: Sending, On the way, Landed, and Home once the lead signs off with your files on their drive. You're not guessing whether it landed, and you're not the one chasing.
Take the link once and never come back, or make a free account and every studio's job turns up in one list. paperwing is paid for by whoever booked the job.
Missing-card check
Transfer tools confirm that what was sent arrived intact. They can't see a card that never left someone's bag. paperwing looks for that too, before anyone formats anything.
Frame numbers. A run of missing numbers usually means a card or folder wasn't selected. A jump too big for that — a reset counter, two cameras numbering alike — is flagged for a look.
Schedule coverage. Key moments with no frames from anyone, like the ceremony or the keynote, are flagged.
Backup cards. Dual-slot copies are recognized and sent once, so they never raise a false alarm.
Findings are prompts, not verdicts. You review them before you sign off.
Sort into moments
The day timeline you set up for the job does double duty. paperwing sorts every file by capture time into moment folders before anything reaches your drive, so the first hour after a wedding isn't spent dragging photos into folders.
Fix where moments blur. Getting ready runs into the first look. Drag the edge and every file on either side follows.
Camera clocks lined up. A second body an hour off because nobody changed time zones is spotted and a correction suggested. Apply it and those frames sort into the right moments.
Receive straight into folders. Numbered moment folders, split by contributor if you like, ready to import into your editor as they are.
Drag an edge. Files follow it into the next folder.
Use cases
The handoff is the same everywhere: private links, fingerprints, a shared manifest, verification and sign-off. What changes is who is shooting and what a missing card looks like.
Four shooters, a dozen cards and one chance at the ceremony exit, handed over in a car park at midnight.
A missing card here: no frames from the first look, or a jump in the second shooter's numbering during the ceremony.
Checked against your day timeline: First look, Ceremony, Family portraits, Grand entrance
Everything in one place
Files are the easy half. The hard half is the six places a shoot actually gets talked about — a text thread, an email chain, a group chat, a comment on a link that expires. In paperwing it happens on the job, next to the files it's about, and it's still there when somebody asks in March what was agreed in September.
A private thread with each person. Just the two of you, about one job. Contributors with an account answer from their own side; nobody else on the job ever sees it.
And one room for everyone on it. Second shooters, the videographer, the editor, the agency. One place to say the entrance moved to 17:45, read by everyone it moved for.
What gets sent stays with the job. A call sheet, a signed release, the JPEG somebody asked for. It files itself into the job's paperwork instead of ending up in a downloads folder.
A question about the shoot, asked where the shoot is. No thread to find, no address to remember.
She answers on the frame itself, with a note pinned to the exact spot. No screenshots, no file names read aloud.
Every job has a room for everyone on it, and a private thread with each of them.
The whole idea
Everyone on a job comes in through their own door and sees only their own part of it — the second shooter, the editor, the agency that booked it. No account, nothing to buy. Their cards arrive fingerprinted, and checked again once they land.
The release goes out from the job and comes back to the job. The question gets asked in the job, in front of the files it is about. Then you pull it all to your drive, sign it off and close it. The copies go. The record stays.
Nobody has to ask who has card B. The job already knows.
After the wrap
The same wedding, after the cards come out of the cameras. Nothing here is a mock-up of a feature we intend to build — it is what the app does.
For contributors
Second shooters, camera operators, freelancers and agency partners are usually tired, on the road, and working to someone else's deadline. So there is nothing to sign up for and nothing to pay.
From a text or email. It already knows the project, the day and who it's for.
Plug in the reader and drop the card folders or camera mags. Backup-card duplicates are spotted and sent once.
Flag a handful of favourites so the lead, editor or client can start on them tonight.
Close the lid if you need to. Transfers resume where they left off.
A live receipt shows exactly where your files are, all the way to sign-off.
Built for the handoff
Everything between the last frame of the day and the first pass in the edit, handled as one job with proof at every step.
Uploads move in confirmed chunks. When hotel Wi-Fi drops or a laptop sleeps, the transfer picks up from the last chunk that landed.
Every contributor's file gets a BLAKE3 fingerprint on their machine. The cloud copy and your local copy are checked against the same list.
Gaps and large jumps in frame or clip numbering, and schedule moments nobody covered, are flagged as prompts to look. Backup-card duplicates are recognised, not flagged.
Contributors star their picks and those files jump the queue, so the sneak peek, same-day social or client preview can start while the full card set is still travelling.
The sign-off button stays locked until every contributor's file on your drive matches its fingerprint. Only an owner or admin can skip that, and their reason goes on the record.
Cloud copies exist to move the job, not to keep it. Closing a signed-off job releases them and frees capacity on your plan.
The handoff
An upload finishing is not the moment to format a card. Every contributor sees exactly which of these four states their files are in, in plain language.
On the way
Every file reached the cloud at its full size. That is a size check, not a fingerprint one yet — though the lead can already start receiving.
On the way
Our server read each stored file back and fingerprinted it again. It matches what your machine recorded before upload.
Landed
The lead has copied the files to their own drive and re-checked each fingerprint there.
Home
The lead signs off once every contributor's file is cloud verified and matches on their drive.
paperwing is a handoff, not a backup. Cloud copies exist to move a job from your team to you, and they are released when you close it. Keep your own backup routine exactly as it is.
Enterprise
The same verified handoff, with the controls a larger organisation needs: a record of who handled every file, sign-in through your identity provider, and policies your admins set once.
2 TB moved per seat each month, pooled across everyone. Past that it's $50 a terabyte — a guardrail, not a second bill. 1 TB kept in the cloud per seat, pooled, then $25 a terabyte a month.
Tell us roughly how many projects and contributors you run, and where files need to end up.
Run every open project and every freelancer, partner and staff shooter in one workspace, grouped by team or client.
Group work by team or client. Each team sets how long its cloud copies are kept, and — if you want it — sees only its own jobs, with everything hanging off them.
Every upload, verification, approval and sign-off recorded with who, when and the fingerprint — hash-chained, so a row that was altered or removed shows up as exactly that. Export the manifest for legal, insurance or delivery records.
Decide who can create projects, invite outside contributors and sign off. Require a second approver before a job is closed and its storage released.
Read your jobs from your production system with an API key, and get a signed webhook the moment a contributor's delivery is cloud verified, so your DAM or MAM can start ingesting from it.
One allowance across the whole organisation rather than a wall per project, so a heavy month in one team borrows from a quiet month in another.
Set up with you, during onboarding: SSO / SAML and SCIM provisioning · Data residency and dedicated storage buckets · Uptime SLA and a named support contact. Each one binds to your identity provider, your region or your contract, so there is nothing to switch on until there is a you.
Pricing
Your files pass through; they don't live here. That's why a terabyte carries a year of work — close a job and its storage comes straight back.
One lead, with contributors sending to you. They never pay and never need an account.
$0/ month
Free forever, no card
$29/ month
Billed monthly
$120per seat / month, billed annually. 12 seats minimum.
For agencies, in-house creative teams and production companies moving files at scale.
Contributors always deliver free — no account, no card, no install. Need more room for a busy month? Any paid plan adds 1 TB for $25 a month.
Questions
Something else on your mind? Email support@getpaperwing.com.
Ready when your cards are
Set up a job in a minute, send the links before you leave the venue or set, and sign off knowing every contributor's file is on your drive and matched its fingerprint there.
Running an agency or production company? See Enterprise