EDIT
☞ runs entirely in your browser — nothing is uploadedDrop your GIF here
or click to browse — animated GIF only
Preview
OneImageTool
Free Image Tools
EDIT
Play it backwards — or forward then back, in one seamless loop.
or click to browse — animated GIF only
Preview
last frame first
Every frame of the animation already exists inside the file. Reversing one is therefore not a rendering job at all — it is decoding the frames, putting them in the opposite order with their delays, and writing the animation back out. Nothing is recomputed, so nothing is lost beyond the re-encode.
The one thing worth getting right is the loop seam. A plain reverse of a clip that already loops cleanly still loops cleanly. A ping-pong — forward then back — repeats the first and last frame if you are careless, and the animation visibly hesitates at both ends. The return trip here drops those two frames, so the turn happens on the beat.
three steps
It is decoded and immediately rebuilt backwards. The preview animates, so you see the result rather than a description of it.
One checkbox turns the reverse into forward-then-back. Useful for a clip with an obvious start and end, where a hard cut back to frame one is jarring.
The rebuilt GIF is saved from your device.
quick answers
The clip plays forward, then backward, then repeats — like a pendulum. It roughly doubles the frame count and the file size, and it removes the jump that a normal loop makes when it snaps from the last frame back to the first.
Yes. Each frame keeps the delay it had, and the delays travel with the frames, so a clip that paused on one frame still pauses on it going backwards.
If the original had no delay set — 0 or 10 ms, which some export tools write — browsers do not play it as fast as possible, they substitute 100 ms. That substituted value is what gets written into the new file, so the result matches what you were actually seeing.
The frames are not resampled, but the GIF is re-encoded, which means a new palette is chosen. On most clips this is invisible. On heavy gradients you may see slight banding.
Not here. Split it into frames first with the GIF to frames tool, drop the ones you do not want, and rebuild with images to GIF.
No. Decoding, reordering and re-encoding all happen in the page, on your device.