Is my GIF uploaded to a server?
No. The file is parsed entirely in your browser, and it's never modified either — this is a read-only inspector.
GIF Analyzer & Frame Inspector
See exactly what's inside a GIF: dimensions, frame count, total duration, loop settings, the global color table, and a frame-by-frame breakdown of delays, disposal methods, and transparency. Read-only and fully local — nothing is modified or uploaded.
Frequently asked questions
What is a GIF disposal method?
It tells the player what to do with a frame before drawing the next one: keep it (draw on top), restore the background (clear the area), or restore the previous frame. Wrong disposal flags are a common cause of ghosting and flicker in animated GIFs.
Why do my GIF frames have different delays?
Each GIF frame stores its own delay in 10ms steps, so encoders often vary them — that's how a GIF can pause on one frame. Note that most browsers treat delays below 20ms as 100ms, which is why some "fast" GIFs play slower than expected.
What does the loop count mean?
It comes from the NETSCAPE extension: 0 means loop forever, a number means play that many times, and if the extension is missing the GIF plays only once. This tool shows you exactly which case your file is.
What's the difference between a global and a local color table?
A global color table is shared by all frames, while any frame can carry its own local table of up to 256 colors. GIFs with many local tables can exceed 256 colors overall — the frame table here shows the global palette and per-frame structure so you can tell how a file is built.
Why would I inspect a GIF instead of just playing it?
To debug why it stutters or flickers, check how heavy each frame is before optimizing, verify loop behavior before publishing, or extract its exact palette for design work — none of which a normal player shows you.