Gallery numbers look arbitrary. They aren't. A catalogue picking an identifier scheme is choosing between four properties that fight each other, and a short sequential number is one specific answer to that fight.
The four properties that conflict
Every identifier scheme wants to be short, unguessable, permanent, and easy to say out loud. You can have about two of those at once.
A long random string is unguessable and permanent but nobody can read it over a phone. A sequential number is short and speakable but tells anyone who looks roughly how big your collection is and when an entry was added. A hash of the content is permanent but changes if you re-encode the file.
Catalogues in this space overwhelmingly picked short and speakable, because their users share references conversationally. That decision explains almost everything else about how these numbers behave.
What sequential numbering costs
Three costs, all real. First, information leakage: a sequential ID tells you the size and growth rate of the catalogue, which is business information most sites would rather not publish.
Second, scraping. If IDs run from one upward, enumerating the entire catalogue is a loop. Every large sequential library gets copied wholesale, which is part of why mirrors appear so quickly after any takedown.
Third, reuse pressure. When entries are removed, the numbers sit empty, and eventually somebody suggests recycling them. Doing that silently breaks every existing reference, which is one of the failure modes in our piece on why shared codes stop working.
| Scheme | Short | Unguessable | Speakable | Stable |
|---|---|---|---|---|
| Sequential number | Yes | No | Yes | Only if never reused |
| Random string | No | Yes | No | Yes |
| Content hash | No | Yes | No | Breaks on re-encode |
| Number plus internal key | Yes | Partly | Yes | Yes |
Why six digits specifically
Six digits is a comfort zone rather than a standard. It holds a million entries, fits in short-term memory the way a phone number does, and stays typeable on a phone keyboard without errors.
Below five digits a growing catalogue runs out fast. Above seven, people start mistyping and stop sharing them aloud. So most catalogues that grew organically drifted into the same range without coordinating, which is why the format feels standardised when it never was.
Running out is the interesting failure. Adding a digit is technically trivial and socially disruptive: every printed, memorised, or pasted reference now has an ambiguous length, and old links have to keep resolving forever.
What better systems do
The usual modern answer is to run two identifiers side by side. A short public number for humans, and a stable internal key that never changes even when the public numbering is reorganised.
Then the rules are simple: retire public numbers permanently, redirect old ones to the internal key, and display full metadata beside every entry so a broken pointer still leaves a usable record. Those six fields are the subject of our piece on the metadata a number can't carry.
Age verification sits in front of all of it. An identifier should never resolve to explicit content before the gate has run, which is a platform responsibility rather than something a catalogue front end can improvise.
What the numbering scheme tells you about a site
You can read a fair amount from how a site handles its numbers. Do old identifiers still resolve? Is there metadata beside each one? Is the artist credited? Does the gate load first?
A site that answers yes to all four is being run by someone who thinks in terms of a library. A site that shows a number and a thumbnail and nothing else usually isn't licensing anything or checking anything, and that's the same category of site where credit gets stripped and moderation is thin.
Our own standards for adult material are written out in the control room, and connected creation, accounts, and safety enforcement stay with the source platform through the production booth and the public tools at models.
Reading a gallery number as a design choice
A six-digit gallery number isn't a code in any meaningful sense. It's a compromise between being short enough to say and long enough to last, made by people optimising for conversation.
Knowing that reframes the whole thing. The number isn't hiding information; it's carrying almost none, by design. Everything you actually want to keep lives in the metadata beside it.