How to read export progress and know what is happening
Sitting at 90% for two minutes with no movement feels identical to being crashed. I could not tell whether to wait or start over. Rendering video in the browser is real work. Forgefy shows honest progress, names which format it is on, and keeps moving the number so you can tell the difference between slow and stuck.
Step 1: Schedule your post. The modal closes and the badge takes over.
Schedule your post. The modal closes and the badge takes over.
Step 2: Read the badge: it shows a percentage and which format it is on, for example fo…
Read the badge: it shows a percentage and which format it is on, for example format 2 of 5.
Step 3: Leave the tab open where possible. Rendering happens in your browser.
Leave the tab open where possible. Rendering happens in your browser.
Step 4: If it truly stalls, the post is marked failed with a reason rather than spinnin…
If it truly stalls, the post is marked failed with a reason rather than spinning forever.
Good to know
One heavy encode runs at a time on purpose. Two parallel encodes fight over the same memory and both get slower. Platforms that accept your source shape are published without re-encoding, which is the fastest possible path. Identical variants are rendered once and reused, so five platforms needing the same shape cost one render. A long pause near the end is usually the final re-encode and the pre-upload defect check.
Can I close the tab?
Better not to during a render. If you do, a server-side safety net still bumps the schedule so a finished render does not miss its slot.
Why was the second export of the same video much faster?
The optimised master and the audio pass are cached, so repeat work is skipped.
Related