Initializing... drag & drop files here
Supports: DNG
This walks through turning Adobe DNG camera RAW files into GIF images — one photo into a single still GIF, or a burst of photos into one animated GIF. It also covers the part most converters skip: GIF holds a maximum of 256 colours per frame, so a continuous-tone RAW photograph will band and dither. By the end you will know which controls actually change the output, why your GIF looks grainy, and when a different target is the honest answer.
.dng files onto the page or click "+ Add Files". One file produces a single still GIF; several files with "Combine?" left on "Single animation" produce one animated GIF, in the order the files are listed.The single most confusing thing about this conversion is that it takes two different routes depending on how many files you upload.
| Colors setting | Realistic result on a photograph | Use when |
|---|---|---|
| ORIGINAL (256) | Best GIF a photo can look; still shows banding in skies | Default — always start here |
| 128 | Noticeably coarser gradients, dither grain more visible | You need a smaller file and the subject is simple |
| 64 | Skin and sky break into patches | Graphics, logos, screenshots inside the RAW |
| 32 or 16 | Poster-like flattening, obvious colour shifts | Deliberate retro or icon-like output |
| 8, 4, or 2 | Near-monochrome abstraction | Silhouettes, masks, novelty effects |
| Format | Colours | Compression | Sensible for a RAW photo? |
|---|---|---|---|
| GIF | 256, indexed | Lossless LZW after quantisation | Only for legacy uploaders or a quick preview |
| JPG | 16.7 million | Lossy DCT | Yes — the normal delivery format for photos |
| PNG | 16.7 million | Lossless | Yes, when you want no generation loss |
| WebP | 16.7 million | Lossy or lossless | Yes — smaller than JPG at similar quality |
| APNG | 16.7 million | Lossless, animated | Yes, when you need an animation to look right |
If the DNG is a frame pulled out of a CinemaDNG or Blackmagic RAW sequence, converting one file here just gives you that one frame; the sequence workflow belongs in software that reads the whole folder. If the file is a proprietary RAW that was merely renamed to .dng, or was truncated during card transfer, decoding can fail outright — re-export a clean DNG from your camera software first. And if what you actually want is a good-looking animation rather than a maximally compatible one, build an APNG from your DNG frames instead: truecolour, lossless, and supported by roughly 96% of tracked browser traffic.
Two separate effects stack. Banding comes from quantisation — millions of captured colours are mapped onto at most 256 palette entries, so gradients become visible steps. Graininess comes from Floyd–Steinberg dithering, which mixes neighbouring palette colours to disguise those steps. Both are inherent to writing a photograph into an indexed-colour format, not a fault in the conversion.
No. One photo is one frame. Animation needs a sequence, so upload the whole burst or timelapse and leave "Combine?" on "Single animation"; the files are used as frames in the order they are listed.
Not on the still-image path. GIF has no JPEG-style quality parameter, so a one-file conversion is governed by the Colors palette and the output resolution. The slider does take effect when several files are combined into an animation, because that path runs through an encoder that accepts a quality target.
In order of effectiveness: reduce Image resolution, then cut the number of frames, then reduce the Colors palette (resolution and palette both live under File Compression → Custom). Photographic content resists GIF's compression because almost every pixel changes between frames, so pixel count is the biggest lever. For an existing file, the GIF compressor applies palette and frame optimisations directly.
There is nothing to keep — a DNG is an opaque sensor capture with no alpha channel. GIF itself only supports 1-bit transparency (a pixel is either fully transparent or fully opaque), so even with a transparent source you would get hard, jagged edges rather than a smooth cut-out.
Yes, permanently in the exported file. Rendering to GIF bakes the current white balance, exposure, and tone curve into flat indexed pixels. Keep the original .dng as your master; treat the GIF as a disposable export.
Three honest cases: an upload form or legacy system that accepts only .gif; a small looping animation assembled from a photo burst where compatibility beats fidelity; and quick throwaway previews. For anything you want people to actually look at, JPG, PNG, or WebP will look far better at a similar or smaller size.
Your files travel over an encrypted connection, are converted on our servers, and are deleted automatically after a few hours. No sign-up, no watermark, and nothing is shared or made public. The realistic limit when uploading a long RAW burst is upload size and time, not the number of frames.