Initializing... drag & drop files here
Supports: HEVC
A .hevc file is a raw H.265 video bitstream — the bare compressed stream an encoder or DVR writes out, with no container and no audio. This tool decodes one frame from that stream and saves it as a TIFF: a lossless raster image meant for archiving and print, not for codec efficiency. The pairing exists for one reason — pulling a reference-quality still out of H.265 footage without adding a second round of lossy compression on top of what the codec already did.
Because TIFF stores pixels losslessly, the frame you extract holds exactly what the decoder reconstructed from the H.265 stream — no extra JPEG-style degradation layered on top. That makes it the right pick for a narrow set of jobs: a golden-frame reference for codec QA (comparing an x265 build's output against a known-good capture), an archival still pulled from H.265 master footage, or any frame headed for print or precision editing where every pixel matters.
It is the wrong pick for sharing. TIFF is not a web format — MDN lists it among image types to avoid for web content, and no mainstream browser except Safari renders a .tiff natively in an <img> tag. 1 A single uncompressed 4K frame is roughly 25 MB, so a folder of them is enormous. If you want a frame to post, email, or drop into a CMS, extract to HEVC to JPG instead; if you need the whole clip to play, use HEVC to MP4.
| Property | Value |
|---|---|
| Standard | ITU-T H.265 / ISO/IEC 23008-2 (standardized 2013) 2 |
What .hevc is |
Raw H.265 elementary stream — no container, no index, no audio |
| Typical producers | x265 / FFmpeg test builds, hardware encoders, some DVR and capture chips |
| Plays in normal players? | Usually no — there is no container or timing index to seek against |
| Audio | None — HEVC is a video-only codec, irrelevant for still extraction |
| Frame structure | Long GOPs: IDR keyframes plus P/B frames that reference them |
| Property | Value |
|---|---|
| Format | TIFF (Tagged Image File Format), raster |
| Released | 12 September 1986 (Aldus); current revision TIFF 6.0, 3 June 1992 3 |
| Specification owner | Adobe (acquired Aldus in 1994) 3 |
| Compression | Lossless: None, LZW, Deflate/ZIP, PackBits. Lossy JPEG also defined. 3 |
| Bit depth | Up to 16 bits per channel; suits high-precision and scientific imaging 3 |
| Native browser support | None except Safari; "avoid for web content" per MDN 1 |
| Best for | Archival stills, print, codec-QA reference frames, precision editing |
.tif vs .tiff |
Identical format — .tif is the legacy DOS/Windows 8.3 three-letter spelling 4 |
.hevc file onto the page or click "+ Add Files". You can queue several raw streams and process them with the same settings.2.100 captures the frame at 2.1 seconds. (Switching to Multiple Screenshots instead returns a series of separate TIFFs as a ZIP, one file per frame — not a single multi-page TIFF.)The TIFF stores the decoded frame without adding any further loss, but it cannot recover detail H.265 already discarded. HEVC is a lossy codec, so the frame the decoder reconstructs is what you get — the TIFF preserves those exact pixels verbatim. Think of TIFF here as a faithful, re-editable container for whatever the codec produced, not a way to undo the original compression.
Both are lossless, so neither changes image quality. The practical trade-off is size versus speed: Deflate/ZIP typically produces a smaller file than LZW, while LZW encodes noticeably faster. 5 LZW's size disadvantage tends to widen on high-bit-depth frames, so prefer Deflate for 16-bit output and reach for LZW when you want a fast, lightly-compressed 8-bit still. Pick None only when you need maximum compatibility with older software that chokes on compressed TIFF.
None — they are the same Tagged Image File Format with two spellings of the same extension. The three-letter .tif dates back to MS-DOS and early Windows, which capped extensions at three characters (the 8.3 filename rule); .tiff is the modern four-letter form. 4 The bytes inside are identical, so use whichever your other tools expect. This page lets you toggle between them, and there is a dedicated HEVC to TIF converter if you specifically want the .tif spelling.
No — this tool writes one image per file. The TIFF format itself can hold several images in a single file, but here Multiple Screenshots mode returns each extracted frame as its own TIFF, delivered together as a ZIP. That keeps each archival still independently usable. If you need many frames, set a sensible interval rather than every frame: a one-minute 4K clip at 30 fps is 1,800 frames, and uncompressed those run roughly 25 MB each.
Because TIFF was never a web display format. MDN explicitly lists it among image types to avoid for web content, and outside of Safari no major browser renders a .tiff inside an <img> tag without an extension or a JavaScript decoder. 1 TIFF is built for downloadable print and precision-editing files. If your goal is on-screen viewing or posting, extract to HEVC to JPG, which every browser displays.
It can, if you ask for a frame right at the very start. HEVC uses long groups of pictures — one IDR keyframe followed by many frames that reference it — so on some streams the decoder needs a complete keyframe before it can render a clean picture. If 0.000 looks wrong, nudge the Time (seconds) value forward by 0.1–0.5 seconds to land on or after the first keyframe.
In our testing, a 4K (3840×2160) frame saved as an uncompressed 8-bit RGB TIFF lands near 24–25 MB, matching the raw pixel math (3840 × 2160 × 3 bytes ≈ 24.9 MB). Switching the Compression Type to LZW or Deflate typically trims that by roughly 30–50% on natural-image content with zero quality loss, which is why we leave lossless compression on for archival stills rather than writing uncompressed.
Usually little to none, because a raw .hevc file is just the coded video — it carries no container-level metadata, no EXIF, and no creation date the way a .mov or .mp4 does. There is nothing in the elementary stream to copy a capture date or GPS tag from. If you need that metadata preserved, start from the original container file rather than the stripped .hevc stream.
Your file is uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after conversion — no sign-up, no watermark, never shared or made public.