A code is the strongest handle you can have on a release, because it is assigned by the studio and travels with the title across every catalogue that lists it. Text lookup on a code beats any visual method — it is exact, fast, and does not depend on image quality.
The failures are almost never "the code doesn't exist". They are formatting mismatches: you typed one form, the catalogue stores another, and a literal text search returned nothing.
What is a code actually made of?
Two parts, sometimes three: a label prefix in letters, a serial number in digits, and an optional suffix marking a variant.
| Part | Example shape | What it tells you |
|---|---|---|
| Label prefix | SSIS, MIDV, IPZZ |
Which studio label released it |
| Separator | - or nothing or a space |
Display convention only — carries no meaning |
| Serial | 001, 0123 |
Sequence within that label; padding varies by catalogue |
| Suffix | -C, -4K, -U |
A variant edition, sometimes added by a distributor rather than the studio |
The prefix is the part that identifies the studio. A few of the widely-used ones:
| Label | Current prefix | Earlier prefix you will still meet |
|---|---|---|
| S1 | SNOS |
SONE, SSIS |
| MOODYZ | MIDA |
MIDV |
| IdeaPocket | IPZZ |
— |
| SOD Create | START |
STARS |
| PRESTIGE | ABF |
— |
| Tameike Goro | MFYD |
MEYD |
Prefixes rotate. A label numbers a line up to 999 and then starts a new one,
so an "old" prefix is not wrong — it simply belongs to a closed run, and every
title released under it keeps that code forever. Checked against the labels'
own catalogues, 2026-08-03; the full table lives in our
studio code reference.
Two notes on suffixes. -C conventionally marks a subtitled edition and 4K
marks a higher-resolution edition. Markers like -U are applied by
distributors to unofficial variants, and their presence is a signal that you
are looking at a re-encode rather than an official release — which matters if
you care whether the source is legitimate.
What are the steps to search a code?
- Read the code exactly, including leading zeros.
SSIS-001andSSIS-01are different strings even when they mean the same release. - Normalise to
LETTERS-DIGITS, uppercase, single hyphen. This is the most commonly indexed form and the right first attempt. - Search it. If a catalogue supports code lookup, this resolves in one step.
- If nothing returns, vary the form before varying the code. Try no separator, a space, and the serial with and without zero padding.
- Strip any suffix and retry. A search for
ABCD-123-Cfails on catalogues that store the base release asABCD-123. - Check the prefix for a lookalike error.
0/Oand1/Iare the usual culprits when the code was read off a low-resolution frame. - If the code still returns nothing, fall back to the face. A frame from the video identifies the performer, and the performer's filmography gets you back to the title.
Which formatting variants should you actually try?
In this order, because they cover most catalogue conventions:
| Attempt | Form | Typical catalogue that uses it |
|---|---|---|
| 1 | ABCD-123 |
Most databases and aggregators |
| 2 | ABCD123 |
Filenames, search boxes that ignore punctuation |
| 3 | ABCD-00123 |
Official catalogues using fixed-width serials |
| 4 | abcd-123 |
Case-insensitive systems — harmless to try |
| 5 | ABCD 123 |
Some listings use a space |
| 6 | ABCD-123 with suffix removed |
Where you started from a variant filename |
If all six fail, the code is either misread or the release is not in that catalogue. Retyping it a seventh way will not change the outcome.
Why do codes sometimes fail even when they are correct?
Because a code identifies a release, and catalogues index what they hold — not what exists.
The same title can appear under a studio code in an official catalogue, under a different code convention in an aggregator, and under a translated title with no code at all somewhere else. A search that matches literal strings misses every form you did not type. This is the same divergence that affects names: in our own performer data, 197 records have an English rendering that differs from the primary name form, which means the same person is findable under two spellings depending on the source you started from.
What if you have no code at all?
Then work backwards from the face, and use the code as the confirmation rather than the query.
A single frame with a visible face identifies the performer. From the performer you get a filmography, and from the filmography you narrow by scene detail — setting, wardrobe, hair length, on-screen text — until one title fits. The code then confirms it.
Our index holds 241,792 faces with 2,333 linked to named performers across 106 sites (our index, 2026-08 snapshot), which is what makes that backwards route practical.
Boundary worth stating: our coverage is concentrated — 2,246 of 2,333 named performers have their representative image from a single source, and the index stores faces rather than release records. It can tell you who, reliably enough to be useful; the which title step is still yours to confirm.
Related questions
- Why can't I find the title I'm looking for?
- How to find a performer's titles by name
- How to find a video from a single screenshot
- How to tell an official source from a pirated one
- Common mistakes people make when searching for a source
If the code is unreadable or absent, the face is the faster route. Upload a frame here — detection runs in your browser, the original never leaves your device, and each result shows its similarity score.