Table of Contents
- Getting Started: Performers
- Handling Ambiguous Performers
- Performer Merge Targets
- Set Performance Aliases on Merge
- Performer Image Sort Order
- Performer Image Selection
- Performer Edit Comments
- Check Suspicious Names and Aliases
- Creating Performers
- Performer Images
- Performer Aspect Ratio
- Performer Image Size
- Performer Placeholder Images
- Performer Watermarks / Logos
- Multi-Performer Images
- Hardcore Performer Images
- BDSM Performer Images
- Performer Names and Aliases
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
In addition to the sidebar on the right, the links below will take you to the broad categories within the Performers page. Additional links to more specific sections will also be listed after the jump. The Getting Started section covers all subjects relating to performers, but is limited to advice and explanations. Firm guidelines that you are expected to follow are instead found in the links directly below it. These cover more specific situations within each subject than the Getting Started sections. Breaking them may risk rejected submissions. If you still have any questions, feel free to ask in the #stashbox-general or #ministry-of-truth channel on Discord.
Getting Started: Performers
The following sections are general advice and explanations for potentially confusing aspects in our database for performers. Because they don't represent explicit decisions concerning database management or curation, they do not require formal approval.
- Handling Ambiguous Performers
Currently, only way is to reassign scenes to disambiguated performers individually.
- Performer Merge Targets
Typically, click "Merge" on the entry with the performer name you'd like to keep.
- Set Performance Aliases on Merge
Usually leave box checked unless the merged name is identical to the merge target's name.
- Performer Image Sort Order
Ranked by size (biggest to smallest), with any horizontal (landscape) images at the end.
- Performer Image Selection
Variety is encouraged, allowing for different user preferences and easier identification from throughout a performer's career.
- Performer Edit Comments
Say what you're doing, why you're doing it, and what your sources are.
- Check Suspicious Names and Aliases
Exercise caution with odd looking aliases, particularly those listed on FreeOnes.
Handling Ambiguous Performers
Currently, only way is to reassign scenes to disambiguated performers individually.
Many performer entries are considered "ambiguous", with multiple performers sharing the same entry on StashDB. This happens most often with single names with no last name or initial, for example "Anna" or "Tony". Currently, the only way to handle these is to reassign the performer on every scene individually which can be tedious and time-consuming. This also often requires the creation of multiple performer entries that do not exist separately yet, which slows down the process even more. There are plans to split these problem entries into multiple performers by studio/network to speed up the process with simple merges. This method is not possible yet.
Performer Merge Targets
Typically, click "Merge" on the entry with the performer name you'd like to keep.
When merging, click the blue "Merge" button on the performer entry you would like to keep. This will be the "merge target." Best practice is to use the entry with the preferred primary name as your merge target when possible. In other words, please refrain from merging and renaming if one of the merged performer entries already has the preferred name. This may require merging an entry with more information into an entry with less, so be sure to include any potentially lost information in your merge submission.
Set Performance Aliases on Merge
Usually leave box checked unless the merged name is identical to the merge target's name.
When merging performers, there is a checkbox that says, "Set performance aliases to old name." The performance alias is used to show what name the studio used for that performer on that particular scene at the time of release. When this box is checked, all scenes without a performance alias will fill this field with the pre-merge performer name. Typically, the box should only be unchecked (it's enabled by default) when a merged name is exactly the same as the merge target's name. We don't want StashDB to say "Jane Doe (credited as Jane Doe)" for example. This will sometimes require separating merges into two submissions: one with the box checked and one with it unchecked.
Performer Image Sort Order
Ranked by size (biggest to smallest), with any horizontal (landscape) images at the end.
Images are currently ranked by size. This means the vertical image (portrait orientation) with the largest resolution is shown first, with the rest in descending order. Any horizontal images (landscape orientation) come last, also descending in size. Knowing this, it should be easier to find and recognize images that do not meet our minimum requirements.
Performer Image Selection
Variety is encouraged, allowing for different user preferences and easier identification from throughout a performer's career.
A variety of performer images is welcomed and encouraged. This includes different "looks" from throughout a performer's career as well as various crops and poses. Different hair styles and colors, different body types or ages, with clothes or without clothes, close-up headshots or full body portraits, facing towards the camera or facing away, etc. Images that include distinctive features like tattoos may help with easier identification as well. More options on StashDB means a greater likelihood that users can find an appropriate image for importing into Stash or for identifying performers. Just be sure that any images you add don't violate any of the separate requirements listed below.
Performer Edit Comments
Say what you're doing, why you're doing it, and what your sources are.
Regardless of what kind of edit you're submitting, always include in the comment field what you are doing and why. Bigger or more drastic changes will likely require longer comments, but simple changes likely won't need much. Also please remember to note what you are using as the source of your edit when appropriate. These notes will be helpful when considering further edits in addition to justifying your actions now to those who will be voting on it.
Check Suspicious Names and Aliases
Exercise caution with odd looking aliases, particularly those listed on FreeOnes.
Not all names and aliases listed on external sources are appropriate on StashDB. Aliases must have been used as an official adult credit somewhere to be eligible as a name or alias on StashDB. This disallows legal names in almost all instances. Please see the relevant section of these guidelines for more details on alias requirements.
FreeOnes often uses false primary names for obscure performers as well as suspected legal names as aliases. Because FreeOnes disallows single name performers, some contributors bypass the limitation by fabricating longer names for single name performers. These usually consist of two single name aliases merged into one. FreeOnes will often list suspected legal names of performers. They are not always accurate and they are not always used publicly by the performer. These names are usually very different from the performer's other listed aliases and from typical adult performer names in general, especially when they include middle names. Be skeptical of any FreeOnes name that isn't listed anywhere else, especially if it's a combination of other aliases or if it doesn't seem like a typical adult stage name.
Creating Performers
The following sections have been formally approved unless stated otherwise. Contributors are still expected to follow any unconfirmed guidelines, but should know that they are subject to change in the near future. Failure to follow any of these guidelines may result in rejected submissions.
- Performer Eligibility
Must work with professional studios or have a verified account on at least one adult platform.
Performer Eligibility
Must work with professional studios or have a verified account on at least one adult platform.
Our main concern with performers is with legality. StashDB is not set up in any way to properly vet and verify performer ages by ourselves. We also can’t verify whether performers are consenting to images/videos of themselves being shared. So, we have to rely on others to do this for us. This can be determined two different ways, detailed below. Any performers that do not meet one of these should be rejected or removed. But first, know that any images or scenes that are known to feature underage performers will never be allowed on StashDB. No exceptions.
First, a performer is eligible if they have ever performed for a professional studio that hasn't been banned from StashDB for repeated violations of age or consent. This means any performer from Brazzers, Adult Time, Vixen, Team Skeet, ExCoGi, NVG, etc. is allowed. This also includes classic performers, even if you're not aware of any scenes of theirs currently eligible for inclusion on StashDB.
Amateur and semi-professional performers will need to include at least one verified profile from an adult platform. This includes Pornhub, ManyVids, and OnlyFans. Any other platforms that do not verify the ages and identities of their creators (TikTok, Reddit, Twitter, etc.) are not enough to make a performer eligible for StashDB. Please remember that even if a performer is allowed on StashDB, only scenes from certain amateur platforms will be allowed. For example, performers who have only released content through OnlyFans will not have any scenes eligible for inclusion on StashDB.
Performer Images
The following sections have been formally approved unless stated otherwise. Contributors are still expected to follow any unconfirmed guidelines, but should know that they are subject to change in the near future. Failure to follow any of these guidelines may result in rejected submissions.
- Performer Aspect Ratio
2:3 ratio is preferred for vertical (portrait) images.
- Performer Image Size
Images greater than 1280px will be automatically downscaled, "low quality" images may be rejected or removed.
- Performer Placeholder Images
Anonymous placeholder images should be rejected or removed.
- Performer Watermarks / Logos
It is recommended to edit watermarks or logos out of performer images if possible, but not required.
- Multi-Performer Images
Images with multiple performers should be cropped if possible, rejected or removed if better images are available.
- Hardcore Performer Images
Images with explicit sex acts should be cropped if possible, rejected or removed if better images are available.
- BDSM Performer Images
Images showing extreme BDSM practices should be cropped if possible, rejected or removed if better images are available.
Performer Aspect Ratio
2:3 ratio is preferred for vertical (portrait) images.
Our preferred aspect ratio for vertical images (portrait orientation) is 2:3. For example, a resolution of 800x1200 has a 2:3 ratio. Some images may need to be cropped with a user's choice of image editing software to achieve this ratio. There is no hard requirement for enforcing this ratio at this time.
Unconfirmed guideline, subject to change pending formal approval.
Performer Image Size
Images greater than 1280px will be automatically downscaled, "low quality" images may be rejected or removed.
The maximum size for images in the Stash-Box software is 1280 pixels. Anything larger than that in either dimension will be downscaled automatically to that size. Images may be removed as "low quality" if they are considered too small or blurry if better alternative images are available for the performer. However, no specific minimum resolution has been agreed upon at this time.
Unconfirmed guideline, subject to change pending formal approval.
Performer Placeholder Images
Anonymous placeholder images should be rejected or removed.
Studios will often use anonymous placeholder images when they don't have anything else for a performer. These placeholder images should not be added to StashDB and any existing placeholders should be removed, even if they are the only images available for a performer. When imported into Stash, they can trick filters into thinking a performer has an image attached even though that image is functionally useless.
Performer Watermarks / Logos
It is recommended to edit watermarks or logos out of performer images if possible, but not required.
There is no hard rule regarding watermarks and logos in performer images, but it is still recommended to avoid them if possible. Sometimes, these images can be cropped to remove unwanted watermarks or logos with your choice of image editing software. Some programs will allow you to "heal" the logo to remove it without cropping. If the logo is unobtrusive, "healing" it would create an odd smear, or removing it entirely would result in an awkward crop, then it may be better to leave it as-is.
Multi-Performer Images
Images with multiple performers should be cropped if possible, rejected or removed if better images are available.
Images that contain multiple people should be removed as "low quality" if better alternative images are available for the performer. Sometimes, these images can be cropped to remove unwanted subjects with your choice of image editing software.
Unconfirmed guideline, subject to change pending formal approval.
Hardcore Performer Images
Images with explicit sex acts should be cropped if possible, rejected or removed if better images are available.
Images that contain explicit sex acts should be removed as "low quality" if better alternative images are available for the performer. Sometimes, these images can be cropped to remove hardcore content with your choice of image editing software.
Unconfirmed guideline, subject to change pending formal approval.
BDSM Performer Images
Images showing extreme BDSM practices should be cropped if possible, rejected or removed if better images are available.
Images that contain explicit or extreme BDSM practices should be removed as "low quality" if better alternative images are available for the performer. Images could qualify for removal if they show severe contortions or possible injury to the body. Sometimes, these images can be cropped to remove explicit content with your choice of image editing software.
Performer Names and Aliases
The following sections have been formally approved unless stated otherwise. Contributors are still expected to follow any unconfirmed guidelines, but should know that they are subject to change in the near future. Failure to follow any of these guidelines may result in rejected submissions.
- Preferred Performer Names
Prefer unique names over commonly used aliases, but otherwise no hard rules only suggestions.
- Eligible Performer Aliases
Must have be used as an official adult credit, no legal names allowed except when a stage name is also their given name.
- Disambiguation Formatting
Summary.
Preferred Performer Names
Prefer unique names over commonly used aliases, but otherwise no hard rules only suggestions.
There are no hard guidelines for choosing primary performer names at this time. However, more unique aliases are almost always preferred over common single word names like "Lola" or "Tony". The following should also be taken into consideration: most frequently used alias, most famous/popular alias, most commonly used name on other databases like IAFD, and alias currently/recently preferred by the performer (often determined by social media profiles).
Also be aware that names are only eligible to be primary names if they've been used as an official adult credit, following the same requirements as eligible performer aliases.
Unconfirmed guideline, subject to change pending formal approval.
Eligible Performer Aliases
Must have be used as an official adult credit, no legal names allowed except when a stage name is also their given name.
Performer aliases must be names that have been used as official credits in an adult video performance. They do not have to be names used as performance aliases in a scene already listed on StashDB. This means that names that have been used professionally in non-adult mainstream performances, listed in credits or bylines as a writer or author, used on public social media accounts, or listed in news articles are not eligible to be listed on StashDB unless they've also been used as an official adult credit.
This also means that outside of the rare occasion of someone regularly using their given name instead of a stage name, legal names are not allowed anywhere on StashDB.
Unconfirmed guideline, subject to change pending formal approval.
Disambiguation Formatting
Summary.
Placeholder description, ask on Discord.
Unconfirmed guideline, subject to change pending formal approval.