Why reversing eats memory
Reversing a video is not like trimming or transcoding. To play frames backwards, FFmpeg's reverse filter has to hold every decoded frame of the clip in memory at once, then emit them last-to-first. A few seconds of 1080p footage is hundreds of full-resolution frames sitting in RAM simultaneously. That is fine for short clips, but a 30-second 4K video can blow past what a browser tab is allowed to allocate. The honest rule of thumb: keep it under about 10 seconds and you will be smooth.
Good uses for a reversed clip
The reverse effect earns its keep in a few places. Satisfying loops — pour, then un-pour — are a staple of short-form social. Rewind gags work for product demos ("watch the bug un-happen"). And reversing a build-up shot can make a clean reveal. Because audio is reversed too, spoken clips turn into the classic backwards-talk effect, which is fun but rarely what you want for a real voiceover — mute the track first if you only need the visual rewind.
How to keep it fast
Two things make a reverse run quickly and reliably. First, trim before you reverse — grab only the seconds you actually want to flip rather than feeding in the whole recording. Second, downscale very large source files first; a 720p reverse is dramatically lighter on memory than a 4K one and looks identical on a phone. If a long clip is the goal, do the reverse on a desktop FFmpeg install where there is no browser memory ceiling.
From recording to reverse
Most reversed clips start life as a fresh recording — a quick screen capture or a phone video shot specifically for the effect. If you are recording the source in the first place, Clipy captures a clean, watermark-free clip you can trim down and drop straight into this tool — no signup, no upload round-trip.