How to Export Your OnlyFans and Fansly Data (Messages, Tips & More)

Your data is one of the most valuable assets in a creator business, yet most platforms make it surprisingly hard to get a complete copy of it. Messages, tips, subscriber history, and earnings are the raw material for accounting, analytics, dispute resolution, and migration — but they tend to live locked inside a platform's interface, viewable but not downloadable.

We built a data export feature, modeled on the familiar "Download Your Information" tools from large consumer platforms, so creators and agencies can take a full, structured copy of their data whenever they need it. This guide walks through what you can export, how it works, and how to run your first export.

Why exporting your creator data matters

There are several concrete reasons to keep your own copy of your data, and most agencies eventually need all of them:

• Backup and continuity. Platforms change policies and accounts can be suspended. A local archive means your business records survive whatever happens to a single account.
• Accounting and tax. A clean ledger of tips, pay-per-view sales, and subscriptions by date range makes bookkeeping and tax filing dramatically easier.
• Analytics. Raw message and transaction data lets you build the deeper analyses platforms do not offer — cohort retention, lifetime value, and response-time studies. Our guide to OnlyFans analytics, LTV, and ROI shows what becomes possible once you have the data.
• Migration and diversification. Moving a creator between teams, or expanding to a second platform like Fansly, is far easier with a portable record of the relationship history.
• Ownership. It is your data. You should be able to hold a copy of it.

What you can export

An export is scoped to a single connected account, and you choose exactly which data types to include:

Subscribers, transactions, and fans come straight from your synced data, so they export instantly and at no API cost. Earnings, messages, and media are fetched live from the platform when you run the export, which takes longer and counts against your monthly API quota in proportion to volume. The dashboard shows you this clearly before you start.

Choose a date range and format

Every export accepts an optional date range. Leave it empty to export everything, or set a from/to window — the date pickers also include quick presets for the last 30 days, last 90 days, and the current year. The range applies to time-bound data like messages, transactions, and earnings.

Exports are delivered as a single ZIP archive containing both CSV and JSON for every section. CSV opens directly in Excel, Google Sheets, or any accounting tool; JSON preserves the full structure for developers and data pipelines. You do not have to choose between human-readable and machine-readable — you get both.

What is inside the archive

The ZIP is organized so a person can browse it and a script can parse it:

• A top-level README and a machine-readable manifest that summarizes the export, including how many live API calls it consumed.
• A data folder with subscribers, transactions, fans, and earnings as CSV and JSON.
• A messages folder with one JSON file per conversation, a flat messages spreadsheet, and an index of every conversation.
• A media folder with downloaded images and videos, when media is included.

Messages are stored in a clean, readable shape rather than raw platform payloads. Each message keeps only what matters — the timestamp, direction (sent or received), the plain-text body, price and tip flags where relevant, and any media — so the files stay small and easy to read. A typical message record is a single tidy line carrying its id, time, direction, and text, with extra fields appearing only when they apply.

How the export runs

Because pulling thousands of messages or media files can take minutes, exports run as a background job rather than blocking your browser. You start it and carry on working; progress streams to the dashboard in real time.

While an export runs you can see:

• The current phase — subscribers, transactions, messages, media, and so on.
• For messages, how many conversations are done, how many remain to scrape, and the running message count.
• The number of live API calls the job has consumed so far.

If a job is taking longer than you want, or you started it by mistake, you can stop it at any time — the worker halts at the next safe point and marks the job canceled. Finished exports stay available to download for several days, then are cleaned up automatically.

Step by step: run your first export

1. 1.In the dashboard, select the account you want to export using the account switcher.
2. 2.Open the Export Data page from the sidebar.
3. 3.Pick a date range, or leave it empty for everything.
4. 4.Choose the data types to include. Subscribers, transactions, and fans are free; messages, earnings, and media run live.
5. 5.Optionally toggle Include media files to download images and videos (OnlyFans first; Fansly attachment links are listed in the message files).
6. 6.Select Create export. A progress card appears and updates live.
7. 7.When the job finishes, it shows in your export history with its size and the number of API calls it used. Select Download to grab the ZIP.

A note on privacy and ownership

The export is generated server-side and is only ever accessible to the account that created it — exports are scoped per tenant, and a download link cannot be used to reach another account's archive. Profile exports strip secrets such as passwords and session tokens. Archives expire automatically, so old copies of sensitive data do not linger on our servers indefinitely. What you do with your downloaded copy, of course, is entirely up to you.

Start exporting

Owning a structured copy of your data turns a platform account into a real business asset — one you can back up, analyze, account for, and migrate on your own terms. The export feature makes that a few clicks rather than a manual scraping project.

To try it, open the dashboard and run an export on any connected account. If you are managing data across platforms, our Fansly support guide shows how the same workflow covers Fansly accounts too, and the OnlyFans API documentation explains the underlying endpoints if you would rather automate exports programmatically.

What to do with your exported data

A structured export is only useful once you put it to work. Common workflows:

• Accounting and tax. Drop the transactions CSV into your bookkeeping tool to reconcile tips, pay-per-view sales, and subscriptions by period.
• Creator payouts. Agencies use the per-fan and per-account breakdowns to calculate splits transparently.
• Analytics. Load the messages and transactions JSON into a notebook or BI tool to build cohort retention, lifetime-value, and response-time analyses platforms do not surface. Our guide to OnlyFans analytics, LTV and ROI walks through what becomes possible.
• Migration and handover. When a creator moves between teams, a portable archive of the relationship history makes the transition painless.

Frequently asked questions

What data can I export?

Account profile, subscribers, transactions and tips, fans, earnings, and full message history — each selectable per export. Media (images and videos from messages) is an optional add-on.

What format is the export in?

A single ZIP containing both CSV (for spreadsheets and accounting tools) and JSON (for developers and data pipelines), organized into clear folders with a README and a manifest.

How long does an export take?

Cached data — subscribers, transactions, fans — exports almost instantly. Messages, earnings, and media are fetched live, so a large account can take several minutes. The job runs in the background with live progress and can be stopped at any time.

Does exporting cost API quota?

Subscribers, transactions, and fans are free. Messages, earnings, and media are fetched live and count against your monthly API quota in proportion to volume — the dashboard shows the cost before you start.

Can I export Fansly data too?

Yes. The same workflow covers Fansly accounts — see Fansly API support.