GIF Splitter.
English

Read the animation clock

GIF frame timing: recorded delays and preview playback

Frame numbers tell you order; delays tell you time. Those are different parts of an animation. Understanding them helps you select a useful still, compare preview playback and move a PNG sequence into another editor without assuming that every frame lasts equally long.

Last updated:

1. Frames and time are different

An animated GIF contains image frames in sequence, but each frame can have its own delay. Twenty frames do not imply twenty equal steps or a particular frame rate. A long hold can use one frame with a large delay, while a brief movement can use several short frames. Count describes the available images; duration describes their recorded time.

Two adjacent frames can also produce similar or identical pictures while keeping different delays. Removing one because it looks redundant can change the animation’s timing. For a single exported still, that difference may not matter. For animation analysis or rebuilding a sequence, retain the association between each original frame number and its delay instead of relying only on the number of PNGs.

2. Read GIF delay units

GIF delay values use hundredths of a second, so one unit is 10 milliseconds. The extractor displays the corresponding millisecond value, including zero when present. For example, a recorded delay of eight units appears as 80 ms. The recorded duration shown by this tool is the sum of the frame delays; it is not a measurement of how long your device took to play them.

A zero delay is metadata, not a command your browser can always execute instantaneously. Rendering, timers and playback rules affect the visible result. Read the number as a property of the source file and keep it distinct from measured playback. Looping also needs separate treatment: the duration of one recorded sequence does not tell you whether the original is set to repeat once or indefinitely.

3. Separate recorded time from preview playback

GIF Splitter uses a practical preview rule: delays below 20 ms are played at 100 ms. This keeps very short or zero-delay frames inspectable. Delays of 20 ms or more use their recorded value for the requested preview interval. The delay label and recorded duration remain unchanged; the tool does not rewrite the source GIF or claim that its preview reproduces every browser’s playback behaviour.

Even the requested interval is not a guaranteed wall-clock measurement. Busy devices, background tabs and display refresh can alter when a frame appears. A slow preview therefore does not prove that the GIF contains slow delays. Pause and inspect the displayed values when timing is important. Exported PNG pixels do not change because the preview uses a longer interval.

The four recorded delays are 0, 10, 20 and 80 ms: 110 ms in total. Requested preview intervals total 300 ms under the short-delay rule; neither total is a measured benchmark.
Inspect the four-frame timing example

4. Walk through the timing fixture

The controlled timing example has four recorded delays: 0, 10, 20 and 80 ms. Adding them gives a raw duration of 110 ms. Under this tool’s preview rule, the first two intervals become 100 ms each, while the final two stay at 20 and 80 ms. Their requested preview intervals total 300 ms. These are calculated metadata values, not a measured speed benchmark.

Inspect the four frames individually and compare each delay label with that list. A correct result keeps the zero and 10 ms labels even though playback makes them easier to see. Export all four PNGs and check their original numbering. The PNG sequence should not claim a 110 ms or 300 ms duration on its own, because standalone PNG files contain no per-frame GIF playback schedule.

5. Choose the right still at a transition

Play an animation to locate the event, then pause and move one frame at a time. Look at the picture before and after the candidate. A transition image might be useful for explaining motion, while a settled image may work better in a tutorial thumbnail. A large delay can help identify an intentional hold, but it cannot determine which still best communicates your particular purpose.

The slider selects by frame number, not by elapsed milliseconds. Moving halfway along a sequence therefore does not necessarily show the temporal midpoint. If you need the image associated with a particular recorded time, add the earlier delays and locate the corresponding interval. For zero-delay frames or differing player behaviour, document the selection convention instead of claiming a universal screenshot time.

6. Keep timing alongside PNG sequences

Downloading one PNG saves a still image. Downloading all frames saves ordered still images in a ZIP, with original frame numbers in their names. Neither operation exports a timing manifest or a newly animated file. If another editor imports the sequence at a fixed frame rate, it assigns its own timing. That can make the rebuilt motion differ from a GIF with variable delays.

Before rebuilding an animation, note each required delay and the source’s looping behaviour in your own working notes. Check whether the receiving editor supports per-frame durations, and set them deliberately. Keep a copy of the original GIF for comparison. If you selected only some frames, the original numbers reveal which were omitted; you still need to decide how those omissions affect the intended animation.

7. Why animations appear to run differently

Different GIF players can handle tiny delays differently. Device load and tab visibility introduce further variation, so visual speed alone is not a reliable reading of the file’s timing metadata. Comparing this tool’s preview with a website animation may also compare GIF with video, because some sites substitute a video file. Verify the actual source format before drawing conclusions.

A recorded frame sequence may also contain a long final hold or repeated visual states that make playback seem uneven. Inspect the delay list and neighbouring images to separate an authored pause from a preview scheduling effect. GIF Splitter exposes the original delays but does not offer timing edits, frame interpolation or a promise of synchronized playback across devices. Use an animation editor when those changes are the goal.

8. Troubleshoot timing without changing pixels

If the motion looks slow here, first check for delays below 20 ms and apply the preview rule. If the recorded duration seems surprising, sum the individual labels and look for long holds or zero values. If a reimported PNG sequence plays differently, check the receiving editor’s default frame rate. These checks address timing without unnecessarily rescaling or recompressing the images.

When asking for help, distinguish the recorded delay, the requested preview interval and an observed playback duration. Include the relevant frame numbers and the browser, and use a controlled example when possible. Do not describe the calculated fixture totals as device measurements. For choosing a still, return to the image itself: timing is context for your decision, while the PNG preserves the selected composed pixels.

Understand your GIF before exporting

Practical guides explain transparency, frame timing and the limits that affect PNG and ZIP downloads.