✂️Free Online Tool

Trim HEVC

Trim HEVC (H.265) video by setting start and end times. No re-encoding preserves the efficient HEVC compression. Used by iPhones, Samsung phones, and 4K cameras.

Drop your file here, or browseSupports MP4, MOV, AVI, MKV, WebM, MP3, WAV and more
⚡

Lightning Fast

Process files in seconds with our optimized servers

🎯

Precise Trimming

Set exact start and end points with frame accuracy

💎

No Quality Loss

Maintain original quality with smart re-encoding

How to Trim an HEVC File Online

  1. Upload Your HEVC File: Drag and drop or click "Add Files" to select an HEVC (H.265) file — raw .hevc/.h265 elementary streams from FFmpeg, screen recorders, IP cameras, or .hevc-renamed iPhone captures all work. Batch is supported — drop in multiple HEVC files at once.
  2. Set Start Time and Duration: Enter a start time and a duration to keep. Both fields accept seconds (12.5) or HH:MM:SS.sss format (00:01:30.500) for millisecond precision. Add multiple trim segments to extract several clips from one HEVC stream in a single pass.
  3. Pick Output Settings (Optional): By default the trim is frame-accurate and the video is re-encoded as H.265 at the visually-lossless default preset (CRF 17), keeping HEVC as the output. Pick different settings if you need another codec: choose H.264 (universal compatibility), AV1 (~30% smaller than H.265), VP9, MPEG-4, or stick with HEVC at a different bitrate. Pair with a resolution preset (2160p, 1440p, 1080p, 720p, 480p, percentage, or custom width/height) and a quality preset (Highest → Lowest), CRF slider (18 = visually lossless, 23 = default, 28 = smaller), constant bitrate, or target file-size percentage.
  4. Trim and Download: Click Trim. Files process on our servers — download individually or as a ZIP. No sign-up, no watermark, no length cap on the output.

Why Trim HEVC Files?

HEVC (H.265) is the successor to H.264 — it delivers roughly the same visual quality at half the bitrate, which is why Apple made it the default capture codec on iPhone since iOS 11 (2017), why UHD Blu-ray uses it exclusively, and why most 4K security cameras, drones, and action cams record in it. A raw .hevc file is the elementary stream without a container, common in FFmpeg pipelines, IP-camera dumps, and developer workflows. Trimming decodes the kept range and re-encodes it at the visually-lossless HEVC default (CRF 17), so the cut is frame-accurate and the clip stays true to the source. Common reasons to trim:

  • iPhone HEVC clips for sharing — iPhone 7 onward records H.265 by default (Settings → Camera → Formats → High Efficiency). A 4-minute 4K HEVC capture is ~400 MB; trim to a 30-second highlight before sharing so it slips under Discord 20 MB / WhatsApp 16 MB / Gmail 25 MB caps. For Windows recipients who can't play HEVC without the paid Microsoft codec, follow up with HEVC to MP4 (re-encode to H.264).
  • 4K drone and action-cam footage — DJI Mini 4 Pro, Mavic 3, GoPro Hero 12, and Insta360 Ace Pro all record 4K/60 in HEVC. A 10-minute flight is multi-GB; trim to the cinematic 90-second cut before color grading in DaVinci Resolve or pushing to YouTube.
  • Security and IP-camera review — Reolink, Hikvision, and Dahua cameras export HEVC clips. Trim the 30-second window where the package was delivered out of an 8-hour recording without processing the whole thing.
  • UHD Blu-ray remux extracts — A 2-hour 4K Blu-ray remux is 50-80 GB of HEVC. Trim a single fight scene or musical number down to a small fraction of the size. Note the trim re-encodes, so HDR10 / HDR10+ / Dolby Vision metadata is not reliably preserved — keep the untouched remux if the HDR layer matters.
  • FFmpeg pipeline outputs — Developers and broadcast engineers often work with raw .hevc annexb streams. Trim a segment for analysis, regression testing, or hand-off to a downstream tool without remuxing back into MP4/MKV.
  • Sharing under email and chat caps — Gmail caps at 25 MB, Outlook at 20 MB, Discord at 20 MB free / 50 MB Nitro Basic / 100 MB Boost, WhatsApp at 16 MB. HEVC's compression efficiency means a trimmed 30-60 second 1080p HEVC clip usually fits without further compression.

For repackaging into a more universally playable container, see HEVC to MP4, HEVC to MOV, or Compress HEVC for size-only reduction without trimming.

Default Trim vs Custom Settings — When to Use Which

Property Default settings Custom settings
Speed Proportional to clip length Proportional to clip length and codec
Quality Re-encoded at the visually-lossless HEVC preset (CRF 17) Whatever CRF / bitrate you choose
Cut precision Frame-accurate Frame-accurate
Output codec Stays H.265 / HEVC H.264, H.265, AV1, VP9, MPEG-4, etc.
HDR10 / HDR10+ / Dolby Vision Not reliably preserved through the re-encode Not reliably preserved through the re-encode
Output size Proportional to duration kept Variable by CRF / bitrate
Best for Quick clips at source-matching quality Codec change for compatibility, smaller file

Keyframe layout doesn't limit the cut point: the kept segment is decoded and re-encoded, so the cut lands on the exact frame you specify even though iPhone HEVC captures and UHD Blu-ray remuxes typically place keyframes every 1-2 seconds.

HEVC Trim Quick Guide

Source Typical GOP What the trim does Notes
iPhone HEVC capture (iOS 11+) 1-2 sec Frame-accurate re-encode HEVC output stays ~50% smaller than equivalent H.264
4K drone / action cam (DJI, GoPro) 1-2 sec Frame-accurate re-encode Visually-lossless default keeps the 4K detail
UHD Blu-ray remux (HDR10 / DV) 1-2 sec Frame-accurate re-encode HDR metadata not reliably preserved — keep the source
IP-camera HEVC export 2-5 sec Frame-accurate re-encode Long source GOPs don't limit the cut point
Raw .hevc annexb stream 1-5 sec Frame-accurate re-encode Output stays a raw HEVC stream
HEVC at 10-bit (Main10 profile) 1-2 sec Frame-accurate re-encode Output is standard 8-bit 4:2:0

Frequently Asked Questions

Will trimming my HEVC file lose any quality?

Not visibly. The trim re-encodes the kept range at the visually-lossless HEVC default (CRF 17), so the clip is not bit-identical to the source but is visually indistinguishable from it. The upside of re-encoding is precision: the cut is frame-accurate — it starts exactly at the time you specify instead of snapping to the nearest keyframe. Quality only drops noticeably if you deliberately pick a lower quality preset, a higher CRF, or a smaller resolution.

Will the trimmed HEVC play on my Windows PC?

Windows 10/11 doesn't include an HEVC decoder by default — Microsoft charges $0.99 for the "HEVC Video Extensions" codec from the Microsoft Store. Free workarounds: VLC, MPV, or PotPlayer all decode HEVC out of the box. If your audience is on Windows and you don't want to ask them to install anything, re-encode to H.264 in step 3 or run the trimmed file through HEVC to MP4 afterwards.

Will HDR10 and Dolby Vision metadata survive the trim?

Not reliably. The trim re-encodes the HEVC stream, and HDR10 static metadata, HDR10+ dynamic metadata, and Dolby Vision RPUs generally do not survive a re-encode — expect the trimmed clip to come out as a standard SDR-range stream. It still plays everywhere the source did and looks excellent on ordinary screens, but if triggering HDR mode on your TV is the point, trim with a dedicated HDR-aware desktop workflow and keep the untouched source.

Why does the cut start a second or two off from where I set it?

With XConvert it shouldn't — the trim re-encodes the kept segment, so the cut starts at your exact timestamp. The snap-back you're describing is how stream-copy cutters behave: they can only cut on keyframes (I-frames), and iPhone HEVC and most camera HEVC use a 1-2 second GOP, so those tools rewind to the nearest preceding keyframe. Here the cut is frame-accurate — the exact frame a goal lands, the precise word in a podcast.

Can I trim multiple HEVC clips with the same time range in one batch?

Yes. Drop in multiple HEVC files and the same start time + duration applies to each output — useful for trimming the same 5-second intro off a batch of episode files, or extracting the same window from multiple camera angles of one event. Per-file overrides are also supported if one clip needs a different range. All trimmed files come back as a ZIP.

What's the maximum HEVC file size I can trim?

There's no fixed cap. Trimming runs on our servers, so the practical limit is upload size and connection speed and patience for the upload. Multi-GB iPhone 4K captures and 50-80 GB UHD Blu-ray remuxes both work — competitors like online-video-cutter.com cap free uploads at 4 GB; XConvert does not. Processing time scales with the length of the segment you keep, not the full source duration.

Can I trim a .hevc raw elementary stream (no container)?

Yes. Raw HEVC annexb streams from FFmpeg, screen recorders, or IP-camera exports are accepted directly — XConvert decodes the stream and re-encodes the kept range, so the cut starts exactly at your requested time. The output stays as a raw .hevc stream; if you need it in MP4 or MKV after trimming, use HEVC to MP4 or HEVC to MKV in a second pass.

Will the audio stay in sync after trimming an iPhone HEVC clip?

Yes. iPhone HEVC captures store H.265 video alongside AAC audio in an MOV/MP4 container; the trim re-encodes both from the same start offset, so they stay aligned to the new start time — XConvert handles the timestamp alignment automatically. Slow-motion clips keep their audio in sync as well, though the slow-mo metadata flag itself may not survive the re-encode.

Should I trim first or convert to MP4 first?

Trim first. Trimming only processes the portion you keep, shrinking the source from a multi-GB file down to just the clip you want. Running HEVC to MP4 on a 4 GB capture is a much slower transcode than running it on the trimmed clip — far faster end-to-end when the conversion involves H.265 → H.264 re-encoding for Windows compatibility.

Rate Trim HEVC Tool

★★★★✭
Rating: 4.8 / 5 - 86 reviews