Skip to main content
Upload media from Automation → Vault → Add Media. Each model needs a linked OnlyFans account belonging to your agency to receive the files during upload.

​
Requirements

  • Access to the model and permission to view and edit its Vault.
  • Messages → Send Messages, Upload Media, and Unsend Messages for that model. Finding the upload recipient also needs Messages → Section View.
  • A separate agency-owned OnlyFans account that the model can message. Your role must allow changing the linked recipient.
  • The original files on your device. One upload wizard accepts up to 300 files, with a displayed limit of 10 GB per file. Check the accepted formats beside the file selector.
The Owner or an administrator can check these rights. Job titles alone do not grant upload access; custom roles and model scope can differ.

​
Upload files

Open Add Media and check OnlyFans Account. Under Fan for uploads, click Bind a fan, enter your agency account’s username or profile link, and click Find. Verify the returned account and confirm Bind. [Screenshot pending: selected model and Fan for uploads account]
Bind only a separate account owned by your agency, never a real fan. Every group of uploaded files is sent to this account in a free direct message. After the media appears in the Vault, AgencyKey deletes that message from the chat; the files stay in the Vault. If deletion fails, follow the displayed instruction to delete the message manually.
The recipient is shared by everyone uploading to this model. Change or Unbind affects the whole team. Changing or removing it during an upload stops the remaining sends. Without a linked, reachable recipient, the upload cannot start.

​
2. Choose and prepare files

Click Add File and select the files. Review the caption, hashtags, suggested price, and tagged creators where needed. Select the rows you want to upload. [Screenshot pending: selected files and upload metadata] A suggested price is Vault metadata; the upload message itself is free. Review duplicates before using Upload anyway. An Already exists item is counted separately from successful uploads and failures.

​
3. Review and start

Click Bulk Upload, review the selection, and confirm Upload. Check the selected model and recipient before proceeding. [Screenshot pending: upload selection and confirmation] After completion, use Add to category to organize the files into your own lists if needed.

​
4. Follow progress

Open the upload status control to see each file and its current state. A file’s row can show the bytes sent and transfer speed. The queue also shows overall speed and an approximate remaining transfer time when enough data is available. These values cover file transfer; OnlyFans processing can continue afterwards. [Screenshot pending: upload progress, waiting state, and file actions] AgencyKey retries temporary transfer failures and can wait for the network or service to recover while the app stays open. Follow the waiting notice instead of repeatedly restarting. A file waiting for final Vault saving does not need a retry unless it reports an error.

​
5. Recover an interrupted upload

After a restart, check Upload interrupted in the Vault header. Choose Add again for the affected model and select the same original file on the same device before the displayed expiry. [Screenshot pending: interrupted upload, expiry, and Add again] Eligible saved uploads can continue by transferring their missing parts. File name, size, and modification date must still match. This does not restore a missing file from the cloud or guarantee recovery after the upload expires or local data is cleared. Forget removes the saved continuation. Canceling an individual file normally removes its continuation too; Cancel upload in the network-wait banner instead keeps the parts already transferred for possible recovery. Keep the original file until the Vault confirms success.

​
Common issues

For a persistent failure, give Support the file name, time, and displayed error details. Review the live Vault and recipient chat before sending the same files again.