FC2 codes identify uploads on a self-publishing marketplace and take the form FC2-PPV-1234567: a platform tag plus a single global serial, with no label prefix at all. Studio codes such as MIDV-123 identify catalogue releases from a production company and encode which label issued them.

That structural difference — global serial versus label-scoped serial — explains almost every practical difference between the two, from what you can infer from a number to how likely it is to still resolve a year later.

How do the two formats differ structurally?

One number is scoped to a label; the other is scoped to an entire platform.

Property Studio code FC2 code
Shape MIDV-123 FC2-PPV-1234567
Prefix meaning Identifies the label or series Identifies the platform only
Serial scope Sequential within one prefix Sequential across all sellers
Issued by A production company The platform, on upload
Digits Usually 3–4 Usually 6–7
Metadata guarantee Catalogued cast, runtime, date Whatever the seller typed
Longevity Persists in catalogues after delisting Disappears when the seller removes it

The digit count alone is a useful first filter. A seven-digit serial is never a studio code, and a three-digit serial is never an FC2 number.

What can you infer from a studio code that you cannot from an FC2 code?

From a studio code you can identify the issuing label; from an FC2 number you can identify nothing but the platform.

IPZZ-123 tells you IdeaPocket issued it, which in turn tells you roughly what production standard, catalogue conventions and release cadence apply. The studio code reference turns any known prefix into that information.

FC2-PPV-1234567 tells you only that somebody uploaded something to FC2's pay-per-view marketplace and got that slot in the queue. The number adjacent to it belongs to an unrelated seller selling unrelated content. There is no prefix to look up because there is no label — the platform is the only common party.

Why does the metadata differ so much in quality?

Because a studio catalogue entry is a business record and an FC2 listing is a seller's own description.

A studio release passes through a production pipeline that produces consistent catalogue data: a fixed runtime, a credited cast, a release date, a series, and cover art in a standard format. Retailers ingest that data, databases mirror it, and the fields stay populated.

An FC2 listing has whatever the seller wrote. Titles are free text, performer credits are optional and frequently absent, runtimes may not be stated, and thumbnails are chosen by the seller. Nothing enforces consistency because nothing has to — the platform sells listings, not catalogue records.

This is why FC2 material is disproportionately the case where people arrive holding a frame and no usable text at all.

Why do FC2 numbers stop working more often?

Because the seller controls the listing, and removal takes one click.

A studio code survives delisting. Even when a title leaves sale, retailer archives, database entries and secondary listings keep the number resolvable, so the code continues to identify the release years later.

An FC2 number is tied to an active listing. When a seller removes it — because they stopped selling, closed the account, or the platform acted — the number loses its anchor. It does not become invalid, but the only authoritative record of what it referred to is gone. That is the most common reason an FC2 lookup fails while a studio code with the same age still works.

How do FC2 codes compare to amateur series codes?

They occupy the same space but are numbered on opposite principles.

Family Example Who assigns the number
Studio label ABF-042 The production company
Planning / amateur series 259LUXU-1234 The series operator
Individual seller FC2-PPV-1234567 The platform, globally

Amateur series codes sit in the middle: they have a stable series identity with its own conventions and a serial scoped to that series, so they behave much more like studio codes than like FC2 numbers. That structure is covered in how amateur and planning-series codes work.

The one-line distinction: a series code says which series; an FC2 code says which upload.

How should you search each family?

Search a studio code as-is; search an FC2 number on the platform's own catalogue first, and expect the trail to be shorter.

For studio codes:

  1. Strip suffixes and site tags
  2. Search PREFIX-NUMBER exactly
  3. If it fails, check whether the prefix is retired or the ID is a padded internal form

For FC2 numbers:

  1. Keep the full FC2-PPV- prefix — the bare digits are meaningless out of context
  2. Expect fewer mirrors and much thinner metadata
  3. If the listing is gone, no amount of reformulating the number will bring it back

The second case is where identifying the performer becomes the practical route, because there is no catalogue record to fall back on.

What do you do when the number leads nowhere?

Work from the face instead, since it is the only identifier that does not depend on a listing still existing.

Our index compares 512-dimension ArcFace vectors across 241,792 indexed faces, covering 2,333 named performers (our index, 2026-08 snapshot), with a 0.40 similarity threshold calibrated for video stills.

Boundary worth stating: our coverage skews heavily toward material that circulates on aggregator sites. Of 106 indexed sites, only around a dozen carry Japanese-style codes at all, and 2,246 of 2,333 representative images come from one source. Self-published platform uploads are exactly the category most likely to fall outside that, so a miss here is common and expected rather than a sign the performer is unknown.

Related questions