OnlyFans Scraper Pro | Posts, Media & Profiles

OnlyFans Data Extractor

Collect available profile information, posts, and media-card metadata from OnlyFans pages you are authorized to access. Results are stored in an Apify dataset for export or use through the Apify API.

Age, authorization, and privacy

OnlyFans is an adult-content platform. Use this Actor only if you are at least 18 and meet the legal age and access requirements where you live. Collect and use data only with the necessary permission and in accordance with applicable laws and the platform's terms. Access to a page does not by itself grant permission to redistribute its content or personal data.

This Actor does not grant subscriptions or bypass paywalls, login requirements, or access controls. It does not guarantee that every profile or item can be accessed.

What you can collect

Choose one mode per run:

• INFO: Profile name or username, and available information such as bio, location, verification indicator, avatar, cover image, counts, social links, and subscription offers.
• POSTS: Post identifiers, text, available media references, publishing time, likes, pinned status, and author information.
• MEDIA: Media-card identifiers, image or thumbnail URLs, media type, and optional duration, collection count, or video URL.

Fields depend on what the page displays and what your authorized session can access. Empty or missing fields are possible. Counts and verification indicators are extracted observations, not independent verification.

Media mode returns records and references. A video card with a usable thumbnail can be a valid result even when no full-video URL is available. This is not a guarantee of full-video downloads.

Getting started

1. Add the OnlyFans profile URLs you are authorized to process.
2. Select Profile Info, Posts, or Media.
3. Set the item limit and request limit. Review the Actor's current pricing and your run budget before starting.
4. If needed, configure an authorized session using the authentication fields in the input form.
5. Run the Actor and review the dataset. Apify supports exports such as JSON and CSV.

Example input, using a placeholder profile you should replace:

{
  "startUrls": [{ "url": "https://onlyfans.com/your_authorized_profile" }],
  "type": "INFO",
  "maxItems": 20,
  "maxRequestsPerCrawl": 50,
  "nameDataset": false,
  "useRandomDelays": false,
  "proxyConfiguration": { "useApifyProxy": false },
  "dev_custom_headers": [],
  "dev_custom_cookies": []
}

Input options

• startUrls: URLs to process. Use profile URLs for INFO and POSTS, or a profile's /media URL for MEDIA. Choose the matching mode. The default profile is https://onlyfans.com/oftv if input omits this field.
• type: INFO, POSTS, or MEDIA. Default: INFO.
• maxItems: Item limit used by extraction. Default: 20; allowed range: 1–1,000. It is not a spending limit. For POSTS and MEDIA, extraction limits apply within each requested source; the PPE writer also checks the remaining run-level event capacity. INFO does not use maxItems: each requested profile can produce a result. Limit the profile list, maxRequestsPerCrawl, and your run budget when using INFO.
• maxRequestsPerCrawl: Maximum crawler requests. Default: 50; allowed range: 1–100. Retries and platform limits can affect how much data is obtained.
• nameDataset: Save a generated dataset label under DATASET_NAME in the key-value store. This does not rename or select the dataset. Default: false.
• useRandomDelays: Add delays between requests. Default: false; this does not grant additional access.
• proxyConfiguration: Set useApifyProxy to enable Apify Proxy. This implementation uses the default Apify proxy configuration when enabled. It does not pass additional group or country options to the proxy client.
• dev_custom_headers: Optional header entries with key and value, including session-related headers where required.
• dev_custom_cookies: Optional cookie entries with key and value, applied to onlyfans.com.

Authentication and access

Public profile details may be available without a session, but availability is not guaranteed. POSTS and MEDIA require the Actor to detect an active subscription on the page; otherwise those modes return no items for that page. They do not automatically switch to INFO mode.

Only supply session cookies or headers for an account you are authorized to use, and only for content that account may access. The form supports a sess cookie and headers such as user-agent and x-bc; these are inputs, not a guarantee that authentication will succeed. Sessions may expire, and access can change.

Treat session cookies and authentication headers as secrets. Do not put them in shared examples, public tasks, datasets, or messages. Use the platform's available private input protections and review who can access your Actor inputs. No credentials are included in this example.

Results and pay-per-event behavior

The following minimum checks apply when the Actor is running under pay-per-event (PPE) pricing:

• INFO: At least a nonempty extracted name or username, with a valid profile identity matching the requested and final page. An explicit username must match that profile. Optional fields are not required.
• POSTS: A nonempty post ID and either nonempty text or at least one usable HTTP(S) media URL. Missing author information does not invalidate a post. The source page must match the requested profile or search.
• MEDIA: A nonempty media ID and a usable HTTP(S) primary image/thumbnail URL. A video thumbnail alone may satisfy this check. The source profile must match the request.

Candidates with missing required content are skipped rather than submitted as paid results; a mismatched profile is also skipped. A structurally invalid source URL raises a safety error and stops output. Previously saved valid results remain available and may already have been charged. A valid record is saved before its result event is charged. If a write or charge has an uncertain outcome, the run stops rather than blindly repeating that operation; inspect the run status and saved data before deciding what to do next. This does not guarantee an atomic transaction between dataset storage and billing.

The result event is result-item. Check the Actor's current Pricing in Apify for the active pricing model, event prices, and any other configured events. maxItems is not a monetary budget.

• Free / pay-per-usage: The person running the Actor may pay Apify platform usage according to their plan, including compute, storage, and proxy usage.
• Pay-per-event (PPE): The customer pays the configured events. Apify platform usage, including Apify Proxy, is a cost to the Actor developer, not an additional platform or proxy charge to the PPE customer.
• Actor Start: If listed in the active Pricing, this event costs US$0.00005 per start per GB of memory, with a minimum of 1 GB. It can apply even when a run produces no results or fails. This manual does not activate an event or a price; the active Pricing controls the charges.

In PPE mode, unknown or unrecognized profile last_seen and post date values are null rather than an estimated current time. Optional data may still be empty. These PPE validation changes do not change the legacy Free extraction path.

Illustrative minimal post result, not a live sample:

{
  "id": "example-post-id",
  "text": "Example post text",
  "date": null,
  "likes_count": 0,
  "is_pinned": false,
  "media": [],
  "author": { "name": "", "username": "", "avatar": "", "is_verified": false }
}

Limits and troubleshooting

• Site layout, subscription state, authentication, or access restrictions may prevent extraction. The current release has been checked with local simulated pages; live extraction and current site selectors have not been verified as part of this release.
• Optional video URLs are read from a page-level player. They may not reliably identify the selected media card. Verify the association before using a video URL. Do not assume a record contains a full video.
• Profile redirects to a different identity are conservatively rejected in PPE mode. Search results are identified within their source query, so the same post appearing in different queries or feeds may be separate results.
• Use a new run when changing to this release. Deduplication keys from older in-progress runs are not migrated automatically.
• Empty output can mean unavailable content, missing access, changed page structure, or records that did not meet the minimum checks. Review the run status and your authorized access; do not use this Actor to bypass restrictions.

API and integrations

You can retrieve datasets and manage authorized runs through the Apify API or Apify's supported integrations. Keep API tokens private and review the configuration and costs of any schedule or integration you enable.