Skip to main content
OnlyFans images break in your app because media URLs expire. OFAuth returns media URLs proxied through media.ofauth.com. They are safe to embed, but they are not permanent. To show media reliably, either re-read the parent resource (the post, message, or vault item) to get a fresh URL, or turn on Vault+, which stores vault media so it stays available after a session expires. Do not store a media URL in your database and render it days later. Store the id of the parent resource and fetch a fresh URL when you render.

Frequently Asked Questions

Why do OnlyFans media URLs from OFAuth stop working? They expire. Media URLs in Access responses are proxied through media.ofauth.com and have a limited lifetime. Re-read the parent resource to get a fresh one. Can I embed media.ofauth.com URLs directly in an <img> or <video> tag? Yes. They are proxied and safe to embed while they are valid. What is Vault+? Vault+ is OFAuth’s persistent media cache for OnlyFans vault media. On V3 it lives under /v3/vault-plus/* and uses the same bearer token and x-linked-account-id header as Access. Which scopes does Vault+ need? vault:read for GET routes and POST /v3/vault-plus/media/batch. vault:write for adding, syncing, and deleting. Is Vault+ on in Sandbox? Yes. Sandbox accounts always have Vault+ on, and their setting cannot be changed.

How do I refresh an expired media URL?

Treat media URLs as short-lived output of a read, not as data. When an image fails to load, or before you render a stale record, call the same Access operation again and use the new URL.
access() is the helper from Calling Access: it sends Authorization: Bearer and x-linked-account-id. For formats and media fields, see Media.

How do I turn Vault+ on?

Vault+ is on or off at two levels, and both must be on. Test accounts need a paid Developer plan, or the PATCH returns 403 subscription_required.

How do I cache a vault list?

Two routes fill the cache from a current OnlyFans vault list:
  • POST /v3/vault-plus/lists/{listId}/add caches new media from the list. It never deletes.
  • PUT /v3/vault-plus/lists/{listId}/sync makes the cache match the list. It removes media that left the list since the last sync baseline.
The first sync creates a baseline and removes nothing. Later syncs remove only media that was in the previous baseline and is missing now. Media still owned by another cached list for the same linked account is not purged.

How do I read cached media?

Vault+ routes take the raw OnlyFans media id, for example 4492994399, not a variant id such as 4492994399_720. A media object groups its cached variants by label, such as full, thumb, and 720.
GET /v3/vault-plus/media also filters by contentType, duration, creation and cache dates, and supports cursor and sort. GET /v3/vault-plus/status reports cache status for the linked account.

How do I delete cached media?

  • DELETE /v3/vault-plus/media/{mediaId} deletes one cached item.
  • DELETE /v3/vault-plus/media deletes all cached media for the linked account.
Both need vault:write and the x-linked-account-id header.

Learn More