Back to Blog
Use Cases

Cosplay Photographer's Delivery Checklist: Sorting 300 Shots for 20 Cosplayers Without a Meltdown

Published on12 min read
Share

It's midnight after the con, you've got 300 photos, and 20 people are messaging at once

Short version up front, because if you've lived this you don't have time for a slow build-up: don't dump all 300 shots into one shared album and drop the link in a group chat. Convention photography has the same fan-out problem as wedding photography — tiered delivery beats one giant dump every time — except cosplay adds a wrinkle weddings don't have. Your recipients aren't one couple who already know each other; they're 20 cosplayers who've likely never met, each of whom only wants their own shots, and none of whom should be scrolling through everyone else's.

I learned this the hard way, honestly. First con I shot properly, I dumped all 300 photos into one shared album and posted the link in the group chat we'd spun up that afternoon. Three days later my phone wouldn't stop buzzing: "Is this one me?" "Which shots am I in?" "Can you pull out the ones that aren't mine, it feels weird having them there." I spent an entire evening answering messages — more tiring than the actual shoot day.

No more overthinking it: cosplay delivery needs to be sorted per person, not dumped as one timeline-ordered batch.

Split by layer first — raw, edited, preview, same three-tier logic as weddings

This part matters, so slow down for a second.

Cosplay delivery is simpler than weddings in one respect — there's only one type of recipient, the cosplayer themselves. But the same layering logic still applies: raw files, finished edits, and social-ready previews serve different purposes and belong in different places.

Layer Contents Typical size Purpose
Raw layer Every RAW / unedited JPG for one cosplayer 1–5 GB depending on shot count Backup for cosplayers who want to edit their own
Edited layer Color-graded, cropped finals, roughly 10–20 per person 3–15 MB per image The main deliverable — what they'll post on their own socials
Preview layer Compressed thumbnails, quick to open on mobile Under 300 KB per image Lets them pick favorites the same night, or serves as the final deliverable itself

Each layer needs a different home.

Keep raws on Google Drive or an external drive. The edited and preview layers are what this piece is really about — because those two are the ones that need "one password per person" delivery.

5 common delivery methods, and where each one falls apart

Here's where it gets useful.

There are five delivery methods that show up constantly in the cosplay community, and each has a different failure mode. Table first:

Method Strengths Fatal flaw Best for
Google Drive folder Large capacity, permanent storage Requires login, and it's easy to accidentally set "anyone with the link" so 20 people can see each other's photos Raw layer
LINE album No extra account needed, everyone in Taiwan already uses it Built for group sharing, not "one album per person" — gets noisy fast once the group grows Small batches, single-recipient delivery
Posting directly to X / Plurk Fast, gets social reach Equivalent to a public announcement, no buffer if the cosplayer wants to check hair and makeup before it goes public Content already cleared for public posting
WeTransfer One-time link, password-protectable, simple interface Free tier links expire in 3 days, capped at 10 transfers and 3GB total within 30 days, sender needs an account One-off, short-window delivery
Password-protected image hosting Each item gets its own password and expiry, no login required Usually single-file links, no album/grouping feature — 20 people means 20 links to organize Edited and preview layers

Don't nod along too fast at "LINE album" — read the next part first.

Honestly, the problem with LINE albums isn't that they're hard to use. It's that the permission model is built for "one group sharing one batch of photos together," not "a bunch of strangers each grabbing their own slice." Convention photography is exactly the second case. Using the wrong tool for the shape of the problem isn't a LINE problem — it's a layer-selection problem.

Same story with posting straight to Plurk or X — if a cosplayer hasn't seen the final shots yet and you post first, you've effectively made a decision for them they never agreed to. That's a real flashpoint in the cosplay community, and a lot of disputes trace back to exactly this.

WeTransfer's free tier does support password protection, by the way, which surprises people who assume it doesn't. The real constraint is quota: 10 transfers and 3GB total in a rolling 30 days, and the sender needs an account (recipients don't). Stack 20 cosplayers' worth of edited photos and you'll hit that ceiling faster than you'd expect.

If you're used to how North American or European creator communities handle this, it's worth noting Discord servers with per-user channels or Instagram close-friends stories solve a similar "controlled audience" problem — but neither gives you a hard expiry date or a per-recipient password the way a dedicated tool does, which matters if privacy (not just organization) is the actual goal.

The 4-step password-hosting workflow that runs itself

No more stalling — here's the actual process.

Password-protected image hosting (something like lpic.cc) solves exactly the "one password per person" problem — every upload link gets its own password, its own expiry date, its own view-count cap, and nobody needs to log in or add you as a contact to see it. Just click the link.

  1. Sort into piles the night of the shoot. Split the 300 photos into 20 folders by cosplayer, 10–20 edited shots plus preview thumbnails each. This step eats more time than people expect — don't push it to the next day, your memory of who's who is freshest right after the shoot.
  2. Upload one at a time, same password per cosplayer. The upload flow takes one image at a time, but the password field is free text — use the same password for every photo belonging to one person, so they only need to remember one password and click through, instead of re-entering it per image.
  3. Set an expiry date, or a hard view-count limit. For previews you don't need to keep forever, 30 days is plenty — the system reclaims them automatically, no manual cleanup. For sensitive, not-yet-public costume or makeup tests, add a max-view cap too, so the link dies after it's been opened the agreed number of times.
  4. Compile one clean list per person before sending. Format it as "link, then password" as two separate messages rather than one — clearer to read, and it means a copy-paste error on your end doesn't silently break both at once.

That's it. Four steps, no step five.

Bottom line — what password-hosted delivery actually saves you isn't upload time. It's the hours you'd otherwise spend answering "where's my photo" from 20 different people.

3 practical habits against raw-file leaks

Being straight with you: there's no single trick that stops leaks entirely, but these three together get you most of the way there.

Share the preview, not the raw. Only the finished edit goes into a shareable link — raws or unedited files stay on your own drive or private cloud, never touching a share link at all. Once a link leaks, whatever you uploaded to it is exactly what's exposed, no more and no less.

Password plus expiry, together. Password alone isn't enough, because passwords and links tend to get forwarded as a pair. An expiry date means that even if the link does leak, it stops working after a while without you having to go delete anything by hand.

The 8MB per-file cap is a feature, not an annoyance. Free image hosts typically cap file size — on lpic.cc, that's 8MB per image. A modern camera's full-resolution edited JPG can bump right up against that if it hasn't been resized. Which means you can't dump an entire batch of uncompressed originals straight into the host — you're forced to compress or crop first, which keeps the true originals on your own machine by default. The limit is doing you a favor here, not getting in your way.

If a cosplayer's camera embeds GPS location data, a leaked raw file exposes more than the photo itself — it exposes where it was taken. I go into this in more depth in EXIF privacy risks and how to fix them — this matters especially for behind-the-scenes shots taken on someone's phone. If you're delivering to cosplayers in the EU or California, this is also the kind of location metadata that GDPR and CCPA treat as personal data, which is one more reason to strip it before anything leaves your hands.

Where lpic.cc fits for con photography, and where it doesn't

Let's be upfront about what it can't do.

lpic.cc doesn't have an "album" or grouping feature — there's no way to bundle 20 cosplayers' photos into 20 separate folders with one link each. Every upload is its own independent short-code link, so 20 people means 20 links you organize yourself; it won't auto-sort them for you. If what you're picturing is "upload once, get 20 albums automatically," that's not how it currently works.

What it does handle well is "one password per item, its own expiry, no login required": links don't require the cosplayer to register an account or add you as a friend, password-protected content is noindexed from search engines, and anything unviewed for 30 days gets reclaimed automatically instead of sitting around eating quota forever. Full feature rundown is in the lpic.cc feature guide on the blog.

The free tier caps images at 8MB, with a separate cap for video — worth stating up front. Raw-layer storage and large batch backups still belong on Google Drive or an external drive; password-protected hosting is really for the edited and preview layers.

Getting your delivery workflow locked in before convention season peaks makes a real difference. Take a dual-event weekend like the Asia Comic Con x Comic Exhibition (PF45 x RF14, taking place Nov 7–8 at the Taipei Expo Park Dome) — any con with a heavy cosplay turnout means the night after is peak photo-request chaos. Have the process nailed down beforehand, and you won't be fielding the same question from 20 people simultaneously that evening.

FAQ

Q1: Do I really need password-protected hosting? Can't I just send the originals over LINE?

You can, but LINE recompresses images, so quality drops noticeably, and the originals have no expiry and no password — once sent, you can't pull them back. For small volumes (a handful of shots to one person), LINE is fine. Once you're past 20 people at 10-plus shots each, manually sending files one by one is where things start getting lost or sent to the wrong person.

Q2: Does every cosplayer need a genuinely unique password?

Not necessarily — "each person knows their own password" is good enough, it doesn't have to be cryptographically distinct across everyone. A common approach is the event date plus the cosplayer's handle, something memorable that's hard for someone else to guess. The important part is sending the password and the link in separate messages, not bundled into one.

Q3: How long should the expiry window be?

30 days is a reasonable default for edited deliverables — most people confirm receipt within a month of a con wrapping up. For sensitive, not-yet-public costume or makeup previews, shorten that to 3–7 days, or add a view-count cap so the link dies after a single open.

Q4: A cosplayer says the link won't open — what's usually wrong?

Most often it's a mistyped password (case sensitivity, full-width vs half-width characters), second most often a link that got cut off mid-copy. Encourage copy-paste over manual retyping for the link, and pick a password that's easy to type correctly — avoid characters that are easy to visually confuse.

Q5: Is it ever okay to upload raw files to a share link?

Not that it's forbidden outright — it's just not worth it. Raws usually exceed a free host's per-file cap, and they may carry GPS and other EXIF data that a finished edit wouldn't. If a link leaks, a raw exposes a lot more than a processed shot does. Hand off raws in person on a drive, or at minimum use a cloud service with real access controls — skip the public share-link route for this layer entirely.

References

#convention photography#cosplay photography#photo delivery#password protection#image hosting#cosplayer#WeTransfer#privacy protection
M

Written by

Mia Huang

Efficiency Expert

Never takes two steps when one will do — writing time-saving guides for everyone.