Media Stuck on Processing or Verifying, by Platform
Most stuck uploads are not stuck — they are processing, and several platforms are slower than you would believe. But there is one state that genuinely never resolves, and knowing which is which saves a lot of waiting.
Fansly
OnlyFans
Maloum
Brezzels
FanvueHow long is normal
| Platform | Legitimate processing time | The state you will see |
|---|---|---|
| Fansly | Hours, not minutes, for large media | Audio it cannot accept sticks on "Verifying" |
| OnlyFans | Sends before processing completes | Flagged not-ready; duration shows 00:00 until done |
| Maloum | Asynchronous; a post refuses media that is not ready | "Upload is not approved" if you attach too early |
| Brezzels | Post exists immediately, media follows | "Under processing" straight after creating |
| Privacy | Gates the composer until conversion finishes | Continuar stays disabled; then a queue widget |
| Fanvue | Uploads in 6 MiB parts, retries per part | Progress per part, up to a 1.5 GiB file ceiling |
Fansly is the one that surprises people. A large file can genuinely take hours rather than minutes, and it is normally still working rather than stuck. An upload that has been running for forty minutes is not broken.
The one state that never resolves
Fansly, audio, "Verifying".
An invalid or very short audio file does not error on Fansly — it sits on Verifying indefinitely. There is no timeout and no message. If your audio has been Verifying for more than a few minutes, it is not going to finish.
- Stop waiting. This state does not clear on its own.
- Check the file is not extremely short. Very brief clips are the common trigger.
- Export it again as a normal WAV or MP3 at ordinary length. Fansly converts it for you once the file itself is unremarkable.
- Upload again. Do not upload the same file expecting a different outcome.
States that look broken and are not
Four cases where the platform is telling you something normal in an alarming way:
Brezzels: "under processing" right after creating. The post exists. The media is not ready. Both facts are fine.
Brezzels: a scheduled post returns flagged as a preview, with a publish time in the future and a creation time of now. Expected.
OnlyFans: a voice note that shows 00:00. It sent. The duration populates when processing catches up. Do not resend.
Privacy: the redirect happened but the post is not visible. Publishing is queued — watch the status widget move from Processando to Concluído.
Maloum: the ordering constraint
Maloum is stricter than the others here, and it produces a specific error worth recognising.
A post will not accept media that has not finished processing. The interface recognises an "Upload is not approved" response and refuses to create the post. Video readiness arrives asynchronously, so a file that appears in your vault is not necessarily ready to attach.
- Upload to the vault and wait for processing to complete before composing.
- Check video aspect ratio is between 1:3 and 3:1 — an out-of-range video is rejected outright rather than processed.
- Attach, then publish.
One more Maloum detail: media URLs are signed and can be replaced after processing. A URL that worked earlier may stop working. That is normal rather than a sign of a lost file.
Fanvue: the size ceiling
Fanvue uploads in 6 MiB parts with up to six retries per part, each getting a fresh signed URL. The observed client ceiling is 1.5 GiB per file.
If a large video repeatedly fails on Fanvue, that ceiling is the first thing to check — it fails rather than warning you in advance.
Diagnosing in the right order
- How long has it actually been? On Fansly, under an hour on a big file is normal. Elsewhere, more than a few minutes is suspicious.
- Is it audio on Fansly stuck on Verifying? Stop waiting and export the file again.
- Is the state actually an error, or a normal in-progress message? Under-processing, not-ready and queued are all fine.
- Is the file within limits? Fanvue caps at 1.5 GiB; Maloum rejects video outside 1:3 to 3:1.
- Is the format on the accept list? Maloum takes only JPEG, PNG, MP4 and QuickTime in chat. Brezzels accepts WebP on posts but not in chat.
- Only then re-upload. Uploading the same file into the same failure wastes the wait twice.
Format accept lists, where they differ
The inconsistencies that waste the most time:
- Maloum chat takes only JPEG, PNG, MP4 and QuickTime. No GIF, no audio at all — that is a platform limitation, not a processing problem.
- Brezzels accepts WebP on a post but not in chat. Same file, two different answers.
- 4based accepts images and video only in its upload dialog. Audio has to come from the recorder, which caps at two minutes.
- Fanvue's device upload is the most permissive — GIF, JPEG, PNG, WebP, TIFF, most video containers, PDF, and a wide range of audio.
If a file is rejected rather than stuck, the accept list is usually the reason and no amount of waiting helps.
When to just start over
Re-upload rather than wait if:
- Fansly audio has been Verifying for more than a few minutes.
- A file was rejected outright rather than accepted into processing.
- The format is not on the platform's accept list.
- The file exceeds a known ceiling.
Keep waiting if:
- Fansly is processing large video and it has been under an hour.
- Any platform says under-processing, not-ready or queued.
- A duration reads 00:00 on something that has already sent.
For failures that are about mandatory fields rather than media, see my post won't publish.