To post collab content on Fansly, add every person who appears to the Co-Performers page in your Creator Dashboard before you publish: send an on-site request if they are already a Fansly creator, a secure verification link if they are not, or upload their signed consent form and ID yourself, then wait until the record shows Approved. Tagging a creator used to stand in for consent, but Fansly's help centre now says on-site requests replace tags for new collaborations, and you still keep your own copies of the paperwork.
This page covers Fansly's approved methods and the consent rules attached to them. The wider paperwork for a collaboration, such as releases and usage rights, is in our content rights release checklist, and choosing and planning partners is covered in the creator partnership guide. State consent laws are mentioned only where they change what Fansly asks you to do.
Tags, requests and what the terms still say
Fansly's co-performer article introduces the Co-Performers page as the way to document consent and says the on-site request replaces the previous method of using creator tags as proof of consent. Tags already used remain valid, but Fansly encourages requests for everything new and says tagging will eventually stop being accepted as consent. Its tagging article now presents a tag simply as a clickable link to another profile.
The Terms of Service have not caught up in wording. Their Co-Authored Content clause still asks you to tag each depicted creator or otherwise identify the person, and to provide documentation of age, identity and consent on request. The same clause requires you to obtain and keep government ID and written consent for everyone depicted, and lets Fansly hold back co-authored content until everyone has confirmed. Fansly's Creator Hub consent page puts the practical upshot bluntly: tagging is not consent, and even with an on-site request you remain legally required to keep consent documentation on file. Use the Co-Performers page, and keep your own records too.
Method table: which consent route fits
The Co-Performers page offers three options, and the right one depends on where your collaborator stands with Fansly. Every timing figure below comes from the co-performer article linked in the same row.
| Collaborator's situation | Option to choose | What they provide | Timing and review | Withdrawing consent later |
|---|---|---|---|---|
| Already a verified Fansly creator | Request an On-Site Fansly Creator | Acceptance of your request from their Requests tab | The request stays visible to them for 7 days (co-performer article) | A red Revoke button in their Requests tab, effective for future content |
| Not on Fansly but willing to join | Ask them to apply as a creator, then send an on-site request | Their own full creator application | Their application review comes first, then the request | The same Revoke button once they are a creator |
| Not on Fansly and not joining | Invite Someone Not on Fansly | Identity verification and an e-signed consent through Ondato, with no Fansly account created | The invite is valid for 14 days (co-performer article) | The Revocation of Consent form, with ID, sent to Fansly compliance |
| You already hold their signed paperwork | Add Manually | The original consent form file, an ID photo straight from the device and an optional tying photo | Review can take up to 7 days (co-performer article) | The Revocation of Consent form process |
| Collaborator resident in Alabama | Add Manually with the notarised Alabama consent form | All completed pages, including the notary acknowledgement | The same manual review | The Revocation of Consent form process |
Fansly calls the on-site request the fastest route and recommends it whenever possible. A collaborator who joins as a creator goes through the same identity checks you did, which our Fansly creator verification guide explains.
Sending an on-site request
- Open Creator Dashboard > Co-Performers and click Add Co-performer.
- Choose Request an On-Site Fansly Creator and send the request to your collaborator's account.
- Ask them to look for the blue circle beside Co-performers on their dashboard, which turns yellow if compliance also needs something from them.
- They accept from the Requests tab; you then appear under Creators Featuring You on their side.
- Track progress with the Sent filter, which also shows declined and revoked requests.
- Publish only once the collaboration shows as accepted, and keep your own copy of their consent documents.
Inviting someone who is not on Fansly
The secure link suits a collaborator who will appear in your content but has no interest in running a page. According to the co-performer article, you give the link a label that identifies the person in your list and can add a personal message, which they see with your username when they open it. They then verify their identity and e-sign the consent documents through Ondato, a step that neither creates a Fansly account nor makes them a creator.
Once they finish, the submission appears on your Co-Performers dashboard showing their first name, selfie and age. If the invite lapses before they complete it, you send another, so agree a time to do it together rather than emailing the link and hoping.
Adding a co-performer manually
The manual route replaces Fansly's old email process: enter the person's details, click Continue, upload the documents and click Submit for Review. The co-performer article asks for original files, not copies. Download e-signed forms from the signing service or its confirmation email, and upload ID photos and selfies directly from the device that took them, uncropped and unedited, because scans, photos of documents and screenshots usually cannot be accepted and delay review.
A tying photo shows the co-performer holding their government ID and the signed consent form, with their face, the ID and the signature page all clear. It is optional, but Fansly strongly recommends it because it helps show the person signed the form themselves. Check everything before submitting, since details cannot be changed afterwards. Returned submissions arrive with notes and can be found with the Action Needed filter. Each person needs their own documentation; group photos are not accepted.
Collab pre-post checklist
- Every participant has a Co-Performers record, including anyone who is only heard or is not identifiable on camera.
- Each record shows Approved or accepted, not pending or Action Needed.
- Consent covers creating the content, publishing it on Fansly and, if downloads are enabled, downloading it.
- You hold copies of each person's ID and signed consent outside Fansly.
- A written agreement sets out how revenue from the content is split and what happens if someone withdraws consent.
- The filming location meets Fansly's rules on public and private places.
- You do not live in North Carolina, where Fansly bars resident creators from uploading co-performer content.
- Captions tag the collaborator for discovery, never as a substitute for the consent record.
- If the content belongs to another creator's page, you repost it rather than reupload it, unless signed consent covers a reupload.
The consent scope in the third item comes from Fansly's Complaints policy, which says consent to creating intimate content is never sufficient proof of consent to publish it, and applies the requirement to everyone depicted, whether identifiable or not. The location rules are summarised in our Fansly content rules guide. On money, the Terms of Service make you solely responsible for dividing revenue from co-authored content under a private agreement that Fansly will not enforce.
Reposting versus reuploading
Fansly's reposting article draws a firm line. A repost, made with the repost icon on the original post, appears on your timeline credited and linked to the original creator and needs no consent form. A reupload, meaning another creator's content placed directly on your own account, requires signed consent forms from everyone featured, and skipping them may lead to enforcement against your account. When in doubt, the article says, repost.
The same article says collaborative content can be reposted or reuploaded if it includes either a tag or a consent form. That wording appears to predate the move away from tags, so for new collaborations rely on the Co-Performers record rather than the tag.
Retracting consent and handling disputes
A creator who accepted an on-site request can withdraw consent at any time with the Revoke button, but the co-performer article says this applies only to content going forward. For earlier media, Fansly's retracting consent article sets out the process: contact the other creator first and explain the request, complete the official Revocation of Consent form, and email compliance a clear photo of your government ID, the signed form and a photo of you holding both.
Fansly's non-consensual intimate imagery article adds that a clear revocation is treated as binding and that documented prior consent does not prevent removal. Mixed situations, such as agreeing to recording but not publication, or consent given under pressure, go through its separate notice form instead. For the creator who published the content, that means shared material can come down even after you paid to produce it, which is why the written agreement should cover withdrawal before anyone films.
Consent has to be real in the first place. Australia's eSafety Commissioner describes consent on its image-based abuse page as permission given clearly, fully understood and free of pressure, and notes that sharing an image with one person does not give them permission to share it further.
State rules that change the process
Alabama and North Carolina already alter the steps. For Alabama residents, the co-performer article requires notarised consent forms with all completed pages uploaded. For North Carolina, Fansly's HB 805 article says creators resident in the state are prohibited from uploading content featuring co-performers, regardless of whether consent forms are on file, and that a state consent form appears in the upload flow for each qualifying upload. Those are Fansly's readings of the laws; what the laws themselves require is a question for a lawyer.
Limitations of this guide
The steps reflect Fansly's help centre, Creator Hub, Complaints policy and Terms of Service as they read on 1 October 2026, at a point where Fansly is midway through replacing tags with Co-Performers requests and its documents do not yet agree. Expect labels, timings and accepted document types to change, and check the live articles before each new collaboration.
This is general information, not legal advice. Consent, privacy and recording laws vary by country and state, and a platform approval does not make content lawful where you live. Before collaborating across borders or with anyone whose consent you have doubts about, speak to a lawyer, and if you are on the receiving end of content shared without consent, report it to Fansly and to the relevant authority.
SirenCY publishes this guide and works as an OnlyFans management agency based in Melbourne. Creators interested in working with an agency can begin on the SirenCY apply page.