dumpbox.ai
Back to home
Venues and club nights

The night ends at four.The photos arrive on Wednesday.

By the time the material lands, nobody cares about that night any more. And the best photos aren't the photographer's: they belong to people whose number you don't have.

While they're still therecollected in the room, not after
Nobody signs upno app, no account
An archive, not twenty chatsa year of nights in one place

The problem is the delay, not the volume

A night produces photos by the avalanche. The trouble is when they arrive: the photographer delivers on Tuesday or Wednesday, by which time the night has passed, the crowd has already seen everything elsewhere, and you needed it on Monday morning.

Meanwhile the images actually circulating are the ones the crowd took, which came out that same night and which you don't have. They're the only ones showing the room full, and nobody will ever send them to you because nobody has a reason to.

Who's shooting
The photographer takes two hundred.The room takes two thousand.

And the room's are the only ones where you can see what the night was actually like.

The best photos belong to people whose number you don't have

This is what separates a venue from every other case: at a wedding you know the guests, in a club the parents are always the same people. Here the crowd changes every Saturday and is made of strangers who may not come back. The next day you have no channel to ask anyone for anything.

The only useful window is while they're inside. An address on a code at the bar or on the bathroom mirror catches that moment: scan, upload three photos, back to the drink. Whoever wants to take part does it in twenty seconds, whoever doesn't does nothing — and in neither case does anyone have to install an app at two in the morning.

How they're collected
A code at the bar,one on the bathroom mirror.

Where people stand still and look: that's where something gets scanned, not on the dancefloor.

scan → upload
Go deeper
One box per night, or one for the season

Both work, for different purposes. One per night keeps events separate, makes sense when each date has its own name and crowd, and leaves you material already sorted by date without splitting it by hand.

One for the season has less friction: the same code stays printed at the bar for months and nobody has to remember to swap it on a Friday. If the venue has a recurring night, that's almost always the right call — and you split by date later, when you download.

What a customer uploads stays theirs

It needs saying, because nobody in this category says it and sooner or later it costs you: a photo uploaded by someone in the room does not automatically become the venue's material. Whoever took it keeps ownership, and using it to promote the next date is something you ask for — not a right that arrives with the upload.

What you do have, and it matters, is responsibility and control over what comes in through your link: contributions can pass through you before appearing, and a photo comes down when someone asks. This isn't legal advice; it's how the tool is built — and stating next to the code what you'll do with the photos is the simplest way not to have to explain it afterwards.

What's left is an archive, which is the part nobody has

A venue that's been running for three years usually has no place where its nights live: it has folders on the computers of people who have since left, and expired links in work chats. The material existed and now it doesn't.

With a shared place what accumulates stays, downloads whole when you need it, and has no countdown. It's the least eye-catching thing on this page, and the one that's worth most two years later.

What you're left with
Whole files,not a repost of a repost.

Images go in as they were shot, which is the only version that holds up on a big screen.

compressed copywhole file

Frequently asked questions

Do customers have to install anything to upload?
No. They scan the code, it opens in the browser, they upload. At two in the morning every extra step is a step nobody takes, which is why there aren't any.
One box per night or a single one?
One per night keeps the material already split by date; one for the season has less friction, because the same code stays at the bar for months. With a recurring night the second is usually better.
Can I use customers' photos to promote the next night?
Not automatically: whoever uploads keeps ownership of what they shot, and promotional use has to be asked for. The simplest thing is to write next to the code what you'll do with them.
Can I control what ends up in the box?
Yes, contributions can be held and pass through you before becoming visible, and a single photo can be removed. Whoever generates the link is responsible for what comes in, and has the right to take it down.
Do the photos become public?
Only if you decide so. A box can have no public page at all: it's seen by whoever received the address.
Are the images compressed like in a chat?
No, they go in at the size they were shot at. That's the difference between something that holds up on a big screen and a repost of a repost.
What about the photographer I already hire?
They carry on doing their job: this is the part they can't cover, the two thousand photos taken by the people in the room. Both end up in the same place.

Try it on one night

A code at the bar next Saturday, and on Monday you look at what came in. If nothing comes in, you've lost thirty seconds.

Or apply for the beta
Keep reading