GIF is the old animated-image format still everywhere in memes and reactions. Of this whole family it carries the least metadata by far - no EXIF, no GPS block, no camera serial, and no creator or edit-history packet that File X-Ray can find. So the useful question for a GIF is not what it stores about you, but what someone can hide inside one.
Scan a GIF fileFor a GIF the scan reports the technical basics and little else: the GIF version (GIF87a or GIF89a), the pixel dimensions, the colour depth, whether the file carries a global colour table, and a SHA-256 fingerprint of the exact bytes. There is no standard place in a GIF for a camera to write a location or a serial number, and no EXIF or XMP for an editor to leave a name in, so from a privacy standpoint a GIF is one of the safer files to share.
The one thing that genuinely matters is appended data. A GIF ends at a well-defined terminator byte (0x3B); anything stored after it is not part of the picture. That is the classic way to hide a second file - a ZIP, another image, a script - behind something that still opens as a normal animation, and it survives ordinary re-saving. File X-Ray walks the GIF's block structure to find the true end of the image and flags anything past it, naming the kind of file it looks like, and the clean copy drops it while leaving every frame, its timing and its loop behaviour exactly as they were.
It is worth stating plainly what a GIF does and does not carry. It has no EXIF block, so unlike a JPEG or a PNG there is no camera EXIF, no GPS and no maker-note serial to read. What it does have is a Comment Extension and an Application Extension, and both are read here: the corpus GIF this tool is tested against names its scanner make and model and the converting software in the first, and carries an XMP packet and a Nikon colour profile in the second. So a GIF is usually quieter than a photograph, but "a GIF, therefore nothing" is not safe to assume, and it is worth scanning for the same reason anything else is.
This is a selection. The full field manual documents the fields read from each format.
Barely any. A GIF has no EXIF block, so no GPS coordinates and no camera serial, and File X-Ray does not find an XMP creator name or edit history inside one either. The scan reports the GIF version, dimensions and colour depth, a checksum, and - the one thing worth attention - any data appended after the image.
From an identifying-metadata standpoint, largely yes: there is nowhere in a standard GIF for a device to write your location or for an editor to leave a creator name. The one thing worth a look is whether anything has been appended after the image, which the scan will show you.
Yes. Data can be appended after the GIF's terminator (byte 0x3B): the file stays valid as an image while carrying a second file or payload, and it survives ordinary re-saving. File X-Ray walks the GIF's block structure to find the true end of the picture and flags anything past it, and the clean copy strips it.
Drop it onto File X-Ray. It reads the version, dimensions and colour depth, computes a checksum, and flags any appended data - all in your browser, with no upload.
File X-Ray reads GIF files entirely in your browser - the file never leaves your device. For this format you can also download a clean copy with the metadata removed. Scan a file now.