WhatSphere catalogs LGBTQ representation at the level of individual characters rather than as a single yes-or-no flag on a title. A character is recorded here when their sexuality is established on screen as something other than heterosexual or unspecified. Across the catalog the model currently identifies 198 such characters appearing in 106 titles, which on average is a little over one recorded character per title that has any at all.
Counting by character makes it possible to ask sharper questions than a title-level tag allows: how central are these characters to the stories they appear in, how does their sexuality break down, and — for adaptations — whether it matches the source. The aim is description, not scoring: the dataset records what is depicted without ranking it.
How WhatSphere measures this
Each cast entry carries a sexuality field, a billing tier that places the role on a lead-to-cameo scale, and a character archetype. For adaptations, a separate flag records whether a character’s on-screen sexuality matches the source material. A title-level centrality measure captures how prominent LGBTQ characters are to the overall story, from incidental to central. Every figure here is generated by WhatSphere’s scoring model, not by a critic’s judgement. Scores describe who a title appears to be made for and how its content is composed; they are not ratings of quality, and a higher or lower number is never a verdict on whether a title is good.
What the data shows
By sexuality, the most frequently recorded category is Gay, with 108 characters of the 198 total. The remaining categories — covering the rest of the spectrum the model tracks — divide the balance, and the distribution is reported in full on the page above rather than collapsed into a single number.
Billing tier is the more telling cut. Of the characters recorded, 85 are lead roles and the rest sit in supporting, ensemble, or cameo positions. The split between leads and background roles is what separates a story built around an LGBTQ character from one that includes a minor one, and the data keeps those two cases distinct instead of merging them into a single presence flag. Where a title is an adaptation, the source-match field adds a third dimension — whether a character’s sexuality was carried over from the source or introduced for the screen version.
Centrality adds a fourth lens that a headcount cannot. A title in which an LGBTQ character anchors the entire story registers differently on the centrality measure from one in which such a character appears in a single scene, even though both would read identically on a simple yes-or-no presence flag. Recording prominence directly — rather than inferring it from the number of characters — is what lets the data separate a story built around its LGBTQ leads from one that merely includes a minor LGBTQ role.
Caveats and limitations
Two limits matter most. First, sexuality is recorded only when it is established in the work; a character coded ambiguously or never specified is left unspecified rather than guessed, which keeps the count conservative. Second, the source-match flag is only populated where an adaptation’s source has been researched closely enough to compare, so it covers a fraction of the recorded characters and should not be read as a catalog-wide rate. As with every measure here, the totals move as coverage expands.
Why it matters
“Is there representation?” is a far less useful question than “what kind, how central, and faithful to what?” — and only a character-level record can answer the second. By tracking sexuality, billing tier, archetype, and source fidelity separately, WhatSphere lets a reader distinguish a lead from a cameo and an adaptation’s own choice from an inherited one, without reducing any of it to a verdict. The titles linked below are those with the most recorded LGBTQ characters; each page shows the breakdown in context.