Kostenloser GIF-Ersteller

How It Works

1. Upload your image frames. Drop or pick two or more JPG, PNG, or WebP files. Each becomes one frame of the animation, in upload order. The browser reads them locally, nothing is uploaded to a server.
2. Reorder if needed. Click a frame and use Move Up / Move Down to fix the sequence. The animation plays in top-to-bottom order.
3. Set frame timing. The Frame Delay slider sets how long each frame is visible (50–2000 ms). 100 ms = 10 frames per second, 200 ms = 5 fps, 500 ms = a more deliberate slideshow rhythm.
4. Choose loop count and quality. Loop = 0 means infinite loop (the default and what most chat clients expect); 1 plays the animation once. Quality 1 is the best output but slowest to encode; 10–15 is the practical sweet spot.
5. Pick an output width. Auto keeps the source size; 400–1000 px presets downscale every frame to a target width before encoding. Smaller widths produce dramatically smaller files.
6. Click Create GIF and download. Encoding runs in your browser. When the progress bar finishes, the preview appears and the file is one click away.

Have a video clip instead? The dedicated Video-zu-GIF-Konverter tool extracts frames from MP4 / WebM / MOV files. This tool is for the image-sequence flow, screenshots, design mockups, photos that should animate one after another.

A Quick Tour of the GIF Format

The Graphics Interchange Format was released by CompuServe on 15 June 1987, designed by an engineering team led by Steve Wilhite. The 1989 GIF89a revision (still the version every browser parses today) added animation timing, single-bit transparency, and application-specific metadata blocks. Looping animation, the thing GIFs are mostly known for now, was not in the original spec at all: Netscape added it in September 1995 with Navigator 2.0 via the "NETSCAPE2.0" application extension, and that 19-byte block is still how every encoder declares loop count today. Compression is the Lempel-Ziv-Welch (LZW) algorithm; the U.S. LZW patent held by Unisys expired on 20 June 2003 (and on similar dates internationally through mid-2004), so GIF has been patent-free for two decades.

Why GIFs Are Bigger Than You'd Expect

Three structural choices in the format combine to make GIF a heavy way to ship animation in 2026:

• 256 colours per frame. Each frame carries an 8-bit indexed palette, 256 entries drawn from a 24-bit RGB space. Photos and gradients have to be quantised down to that palette, which either loses detail (banding) or spends bytes on dithering patterns to hide the loss.
• No interframe prediction. Modern video codecs store one keyframe and a stream of motion deltas; GIF stores every frame independently. A 30-frame animation is essentially 30 separate compressed images stacked in a file.
• Single-bit transparency. A pixel is either fully opaque or fully transparent. There's no alpha channel, which is why curved shapes against a non-matching background show jagged edges.

The practical consequence: a 5-second 480 px clip is easily 5–20 MB as a GIF but only a few hundred KB as MP4. Most social platforms cap GIFs around 5–15 MB and strip larger ones. If your destination is a modern web page under your own control, an MP4 in <video autoplay muted loop playsinline> is usually a better technical choice. GIF still wins anywhere the destination has unpredictable codec support (chat clients, README files, email signatures, issue-tracker comments) because every reader on every platform can display it without a video player.

Practical Settings to Aim For

The pixel-area rule. File size scales roughly with the number of pixels per frame, which means doubling the output width quadruples the area at the same aspect ratio. A 320 px GIF is roughly a quarter of the size of the same animation at 640 px, and roughly a sixteenth of the size at 1280 px. Always downscale before encoding rather than after.

When to Use GIF, When to Reach for Something Else

• GIF wins when the destination is unpredictable: chat clients, email, GitHub, Notion, Confluence, Jira, ticketing systems. A GIF embedded with a plain <img> tag plays automatically on every browser since the 1990s with no video player markup or codec checks.
• APNG (Animated PNG) was officially folded into the PNG specification in 2023. It supports 24-bit colour and a real 8-bit alpha channel, so curved shapes look clean against any background. Files are usually larger than GIF for the same animation, but quality is far higher.
• Animated WebP is Google's all-purpose animation format with full alpha and lossy/lossless modes. Cross-browser support is around 97% in 2026; chat clients vary (Discord added native animated-WebP support in late 2024; Slack and iMessage are still inconsistent).
• Animated AVIF produces the smallest files of any current format (often an order of magnitude smaller than GIF) but messaging-app and image-editor support still lags behind static AVIF.
• MP4 / WebM video is the right pick for any animation longer than a few seconds destined for a web page under your control. <video autoplay muted loop playsinline> is the standard wrapper. Browser autoplay policies allow muted video without a user gesture, so the visual behaviour is indistinguishable from a GIF at a fraction of the bytes.

Privacy and Speed

Many online GIF makers upload your images to a server, encode there, and serve the result back. From a data-handling perspective that means screenshots of pre-release UI, NDA'd designs, photos of children, or anything else you'd rather not hand to a third party traverses someone else's infrastructure. This tool runs the encoder in your browser via the open-source gif.js library, frames go from drag-and-drop directly to a Web Worker that builds the GIF, and the only thing that leaves the page is the encoded file when you click Download. Speed depends on your device: a quick reaction GIF takes a second or two, a 30-frame slideshow at 800 px might run for 10–15 seconds on a typical laptop.

Common Mistakes

1. Frames at very different sizes. The encoder uses the first frame's dimensions and either letterboxes or stretches the rest. Crop or resize your sources to match before uploading for the cleanest output.
2. Frame delay set as fps. The slider takes milliseconds per frame, not frames per second. 100 ms is 10 fps, 200 ms is 5 fps, and 500 ms is "every half second." If your animation looks slow, try lowering the delay; if it looks frantic, raise it.
3. Quality value misunderstood. Lower numbers are higher quality (and slower); higher numbers are faster but coarser. 10 is a good default; drop to 5 for important hero images, push to 15–20 if file size is critical.
4. Output width too large. Doubling the width quadruples the file size. 480 px is enough for chat and most documentation; reach for 800 px only when text in the GIF needs to stay legible.
5. Loop count of 1 by mistake. Some platforms (notably older Twitter behaviour) display non-looping GIFs as a single static image. Leave Loop = 0 unless you have a specific reason to play once.
6. Mixing PNGs with transparency and JPGs without. JPG frames have an opaque background; PNG frames may be transparent. The encoder picks one transparency colour per palette, so mixed sources can produce unexpected halos. Convert all frames to the same format first.
7. Trying to make a long animation. GIF is a poor format for anything over ~10 seconds, file size becomes unmanageable and most sharing surfaces cap upload size. Trim aggressively, or switch to MP4 / WebP for longer content.

Frequently Asked Questions

How many frames can I add?

As many as your device's memory comfortably holds. The encoder runs entirely in the browser, so there is no server-side limit, but a 100-frame, 1000 px GIF will take a noticeable amount of time to encode and produce a multi-megabyte file. For most use cases, 5–30 frames at 400–600 px is the sweet spot.

What image formats can I upload?

Anything the browser can decode as an image, JPG, PNG, GIF (the first frame is taken), WebP, BMP, and most modern formats. SVG support depends on the browser's canvas API. For the cleanest output, keep all frames in the same format and the same dimensions.

Does the GIF have transparency?

GIF supports single-bit transparency only, a pixel is either fully opaque or fully transparent, with no anti-aliasing. If you upload PNG frames with semi-transparent pixels (drop shadows, soft edges), those translucent regions either snap to opaque or to the chosen transparency colour, which can produce a fringed look. For animations that need clean alpha against arbitrary backgrounds, APNG or animated WebP are better formats, though support varies by destination.

Is the encoded file uploaded anywhere?

No. The gif.js encoder runs in a Web Worker in your browser. Your source images are never sent to a server, and neither is the encoded output. Once the page has loaded, the tool also works offline.

Why is my GIF so large?

GIF compression is poor by modern standards, every frame carries its own 256-colour indexed palette, with no inter-frame prediction. The biggest levers are output width (file size scales with pixel area) and frame count. Cap width at 480 px for chat-friendly output, trim the animation to the essential frames, and bump the quality value toward 15–20 for the smallest files.

Can I edit a GIF that I've already made?

Not directly, this tool builds new GIFs from individual image frames, it does not decompose an existing GIF back into frames. To edit an existing GIF, you would first need to extract its frames as separate images, modify or reorder them, then upload them back here as a new sequence.

Verwandte Tools