免费转换 HEVC 文件

Why do 4K HEVC files download quickly but take forever to encode?

HEVC decoding (playback, downloading) leverages hardware acceleration in modern devices - dedicated silicon handles decompression efficiently. Your phone, TV, computer likely has HEVC decoder chip enabling smooth 4K playback with minimal CPU load. Encoding is different story - creating HEVC requires complex analysis and decision-making that hardware encoders oversimplify for speed. Software encoding (libx265, required for quality) uses CPU exclusively, analyzing every frame exhaustively. A 4K HEVC encode at medium preset can take 20-50 hours for 2-hour movie on typical desktop.

Compression efficiency demands computational cost - HEVC achieves 40-50% better compression than H.264 through sophisticated algorithms: larger block structures (64x64 CTUs), 35 intra prediction modes, advanced motion compensation, context-adaptive coding. These features enable superior compression but require extensive computation during encoding. Encoder tests many possibilities per frame (motion vectors, partition modes, transform sizes) selecting optimal choices. This exhaustive search creates small files but demands massive processing time.

What's the actual difference between HEVC, H.265, and x265?

{faq_2_intro}

{faq_2_privacy_title}

{faq_2_privacy_desc}

{faq_2_instant_title}

{faq_2_instant_desc}

{faq_2_offline_title}

{faq_2_offline_desc}

{faq_2_technology_title}

{faq_2_technology_desc}

{faq_2_outro}

Can I safely convert iPhone HEVC videos to H.264 without losing quality?

{faq_3_intro}

{faq_3_web_title}

{faq_3_web_desc}

{faq_3_photos_title}

{faq_3_photos_desc}

{faq_3_graphics_title}

{faq_3_graphics_desc}

{faq_3_print_title}

{faq_3_print_desc}

{faq_3_social_title}

{faq_3_social_desc}

{faq_3_professional_title}

{faq_3_professional_desc}

{faq_3_mobile_title}

{faq_3_mobile_desc}

{faq_3_outro}

Why do streaming services use HEVC for 4K but YouTube still defaults to VP9?

Patent licensing explains divergence. Netflix, Amazon, Disney+ use HEVC for 4K accepting patent licensing costs because they're subscription services with revenue to cover fees. HEVC's compression efficiency reduces bandwidth costs significantly for 4K streaming - savings exceed licensing expenses. YouTube (Google) avoids HEVC license fees using VP9 (Google-developed, royalty-free codec) with similar compression to HEVC. YouTube's ad-supported model and massive scale make HEVC licensing economically unattractive. Business model determines codec choice as much as technical merit.

Client compatibility factors in - HEVC hardware decode widespread in TVs, streaming boxes, mobile devices purchased 2016+. These devices come with HEVC licenses from manufacturers. VP9 has good software support in browsers (Chrome, Firefox) and some hardware support but less universal than HEVC in dedicated streaming devices. Netflix targets TV/appliance ecosystem where HEVC dominates; YouTube targets web browsers where VP9 integration is native. Platform optimization drives codec selection.

Future convergence toward AV1 - both companies transitioning to AV1 (royalty-free, better compression than HEVC/VP9). YouTube already serves AV1 to supported devices; Netflix testing AV1 deployment. AV1 resolves patent issues while improving compression. Expect HEVC and VP9 to gradually fade as AV1 hardware support reaches critical mass (2023-2026 device generation). For personal encoding, follow streaming services: use HEVC for local media (Plex, personal archive) where licensing doesn't apply to individuals, VP9/AV1 for web content avoiding patent concerns.

How much smaller are HEVC files compared to H.264 really?

Theoretical 40-50% smaller at equivalent quality, practical results vary by content type. High-motion content (sports, action movies) sees 35-45% reduction - HEVC's improved motion compensation shines. Low-motion content (dialogue, animation) sees 45-55% reduction - advanced intra prediction excels with static regions. 4K content benefits more than 1080p - HEVC's large block structures are proportionally more effective at high resolutions. Typical scenario: 10GB H.264 1080p movie becomes 6-7GB HEVC at matched quality. 4K movie: 40GB H.264 becomes 22-25GB HEVC.

Comparison methodology matters - must compare at same perceptual quality not same bitrate or file size. Fair comparison: encode H.264 at CRF 23, encode HEVC adjusting CRF until visual quality matches (usually CRF 26-28 for HEVC matches H.264 CRF 23). Compare file sizes at matched quality. Naive comparison using same CRF value unfair because codecs have different CRF scales. Or use VMAF/SSIM metrics objectively measuring quality, targeting same score with both codecs. Proper comparison confirms HEVC's compression advantage is real and substantial.

Practical impact for users - reclaiming storage from video library. 1TB of H.264 video becomes 550-650GB in HEVC freeing 350-450GB for other content. For 4K collections, savings are massive: single 4K movie at 50GB (H.264) becomes 28-32GB (HEVC), saving 18-22GB per film. 50-movie 4K collection: 2.5TB (H.264) versus 1.4-1.6TB (HEVC), saving 900GB-1.1TB. Trade-off is encoding time - weeks of processing for large library. Calculate value: hours of encoding time versus dollars of storage saved. For most users, storage is cheaper than time. HEVC makes sense for large archives where storage constraints exist or bandwidth costs matter.

Should I use HEVC Main or Main 10 profile for encoding?

Main profile (8-bit color depth) sufficient for most consumer content. Compatible with virtually all HEVC decoders including budget devices. Main 10 profile (10-bit color) reduces banding in gradients and provides slightly better compression efficiency (2-5% smaller files at same quality) due to finer quantization. If source is 8-bit (typical cameras, downloads, broadcasts), encoding in 10-bit requires upconversion during encode providing minimal benefit. Use Main 10 if: source is truly 10-bit (HDR content, professional cameras, high-end captures) or fighting severe banding in 8-bit source.

Compatibility consideration - Main 10 requires slightly more decode power. Older HEVC hardware decoders (2015-2016) might support Main but not Main 10, forcing CPU decode with potential playback issues. Devices from 2017+ generally support Main 10 especially if they support HDR (which requires 10-bit). Check target playback devices: if supporting old hardware, use Main profile; if only modern devices, Main 10 acceptable. For maximum compatibility, Main profile is safer default.

Encoding command distinction: Main profile: `ffmpeg -i input.mp4 -c:v libx265 -crf 26 -pix_fmt yuv420p output.mp4`. Main 10 profile: `ffmpeg -i input.mp4 -c:v libx265 -crf 26 -pix_fmt yuv420p10le output.mp4`. Note `yuv420p10le` specifies 10-bit color. For HDR content, Main 10 mandatory with additional HDR metadata preservation: `-x265-params hdr-opt=1:repeat-headers=1:colorprim=bt2020:transfer=smpte2084:colormatrix=bt2020nc`. Most users should default to 8-bit Main profile unless specific reason for 10-bit. Don't assume higher number means better - use appropriate profile for content and playback targets.

Can I edit HEVC video directly or should I convert to editing codec first?

HEVC is delivery codec not editing codec - highly compressed with complex inter-frame dependencies making frame-accurate editing difficult and playback sluggish. Professional workflow: transcode HEVC to intermediate/mezzanine codec (ProRes, DNxHR, Cineform) optimized for editing, edit in intermediate format, export final delivery in HEVC. Intermediate codecs use intra-frame compression (each frame independently encoded) enabling smooth scrubbing, accurate cuts, realtime effects. File sizes explode (5-10x larger than HEVC) but editing experience transforms from painful to fluid.

Consumer editors (iMovie, DaVinci Resolve, Premiere) can edit HEVC natively if computer has hardware decoder. Performance depends on: CPU/GPU power, HEVC hardware support, resolution (1080p manageable, 4K challenging), timeline complexity. Simple cuts and basic corrections might work acceptably editing HEVC directly. Complex timelines with effects, color grading, multiple layers will struggle. Generate optimized media/proxies (editor-specific terminology for automatic transcoding) if native HEVC editing is sluggish. Editors handle this automatically - enable proxy workflow in preferences.

Decision factors: project complexity, timeline, performance. Quick trim and upload: edit HEVC directly accepting minor inconvenience. Serious project with effects and color work: transcode to editing codec first. Creating proxies: `ffmpeg -i input.hevc -c:v prores_ks -profile:v 2 -c:a pcm_s16le proxy.mov` creates ProRes proxy. Edit proxy file, export with reference to original HEVC if editor supports relinking, or export from proxy accepting minor quality loss. Balance quality, performance, storage based on project requirements. Don't suffer through sluggish HEVC editing for complex projects - transcode and work efficiently.

Why do some TVs play HEVC perfectly while others show errors?

HEVC compatibility nuances causing playback failures:

Profile/Level Mismatch

TV might support HEVC Main profile but not Main 10, or Level 4.0 but not 5.1. Encoding beyond TV's capabilities causes playback failure or "unsupported format" error. Check TV specs: budget models often limited to Main profile Level 4.0 (up to 1080p60 or 4K30). High-end models support Main 10 Level 5.0+ (4K60 HDR). Encoding to TV's maximum capability ensures playback. Use MediaInfo to check file's profile/level: must match or be below TV's specification.

Container Format

HEVC stream might be fine but container problematic. TVs often support HEVC in MP4 and MKV but behavior varies. Some play MP4 but reject MKV. Some support HEVC in USB playback but not DLNA streaming. Test container formats: remux HEVC stream without transcode: `ffmpeg -i video.mkv -c copy video.mp4` changes container keeping codec identical. If MP4 plays but MKV doesn't, container compatibility issue not codec issue. Use working container for TV's media player.

Audio Codec

Video codec supported but audio codec isn't - TV shows error or plays video without audio. HEVC files often use advanced audio (DTS-HD, TrueHD, Opus) that budget TVs don't decode. Solution: ensure audio compatibility by using AC-3 or AAC: `ffmpeg -i input.mkv -c:v copy -c:a aac -b:a 192k output.mp4` keeps HEVC video, converts audio to universal AAC. Verify audio codec with MediaInfo. TVs reliably play AAC and AC-3; other codecs vary by model.

Bitrate/Resolution

File exceeds TV's processing capability - too high bitrate, extreme resolution, high frame rate. TV technically supports HEVC but not at file's specific parameters. 4K 60fps at 100 Mbps might exceed decoder throughput even though TV claims 4K HEVC support. Reduce bitrate or frame rate: `-crf 28` for smaller bitrate, `-r 30` to limit frame rate. TV specifications list maximum bitrate and resolution - stay within those limits.

{faq_8_web_title}

{faq_8_web_desc}

HEVC compatibility isn't binary - many variables affect playback. When TV rejects file, identify specific incompatibility (profile, container, audio, bitrate) and adjust. MediaInfo shows file parameters, TV manual shows supported specifications. Match them.

Is using hardware HEVC encoder worth the quality sacrifice?

Depends on use case. Hardware encoders (NVENC on NVIDIA, QuickSync on Intel, VCE on AMD) encode 10-20x faster than software x265 but produce 15-25% larger files at equivalent quality. For archival or permanent encode where quality per bitrate is critical, software x265 is worth the time. For temporary encodes, quick sharing, iterative workflows, real-time encoding (streaming, recording), hardware encoder's speed advantage outweighs quality compromise. Evaluate based on encode frequency and permanence.

Quality gap closing - recent hardware encoder generations (NVIDIA RTX 40-series, Intel 12th gen+) significantly improved approaching software quality. Gap was 30-40% in early hardware encoders (2016-2018), now 15-20% and closing. High-quality hardware preset modes offer good balance: `ffmpeg -i input.mp4 -c:v hevc_nvenc -preset p7 -cq 23 output.mp4` (NVIDIA) uses highest quality hardware preset competitive with medium-speed software encoding. Test for yourself comparing hardware versus software output - modern hardware encoders often acceptable for non-critical applications.

Hybrid approach - use hardware encoder for initial/temporary encode where speed matters, re-encode important content with software later for archival. Record gameplay with NVENC getting manageable file sizes in real-time, re-encode highlights with x265 for permanent YouTube upload. This two-tier strategy balances immediate needs with long-term quality. Don't dogmatically insist on software encoding when hardware suffices for application. Equally, don't use hardware for permanent archival just because it's faster - invest time for lasting quality.

What HEVC encoding preset should I use for different scenarios?

x265 preset recommendations balancing speed and efficiency:

Fast/Quick Encode

For rapid turnaround (sharing, testing, previews), use `veryfast` or `faster` presets: `ffmpeg -i input.mp4 -c:v libx265 -preset veryfast -crf 26 output.mp4`. Encodes 3-5x faster than default `medium` but produces 15-25% larger files. Quality acceptable for non-critical use. Useful for iterative workflows where you'll encode multiple times, large batch jobs where time matters, or quick social media sharing where compression efficiency less important than delivery speed.

Balanced Encoding

`medium` preset (default) offers good speed/efficiency balance suitable for most users: `ffmpeg -i input.mp4 -c:v libx265 -preset medium -crf 26 output.mp4`. Encodes reasonably fast (2-5fps for 1080p on modern CPU) with good compression. Appropriate for personal media library, content delivery, general purpose use. Sweet spot of diminishing returns - faster presets save time with acceptable size penalty, slower presets gain little compression for significant time cost.

High Efficiency

`slow` or `slower` presets maximize compression for archival, streaming preparation, or storage-constrained scenarios: `ffmpeg -i input.mp4 -c:v libx265 -preset slow -crf 24 output.mp4`. Encodes 2-3x slower than `medium` but produces 5-10% smaller files. Worthwhile for permanent encodes where one-time time investment yields lasting storage savings. For 500-movie library, extra encoding days result in 50-100GB storage reclaimed. Calculate value based on storage cost and encoding capacity (overnight/weekend processing).

Maximum Compression

`veryslow` or `placebo` presets for extreme efficiency needs. `veryslow` is last preset worth using - 3-4x slower than `medium`, 8-12% smaller files. `placebo` is 10x slower than `medium` for 1-2% additional savings - rarely justified. Reserve `veryslow` for bandwidth-constrained distribution (serving video to thousands, limited hosting bandwidth) where compression efficiency has measurable economic value. Personal use: `slow` is practical maximum; `veryslow` for truly precious content; `placebo` for bragging rights only.

{faq_10_unix_title}

{faq_10_unix_desc}

{faq_10_portable_title}

{faq_10_portable_desc}

{faq_10_legacy_title}

{faq_10_legacy_desc}

{faq_10_specialized_title}

{faq_10_specialized_desc}

{faq_10_fax_title}

{faq_10_fax_desc}

{faq_10_retro_title}

{faq_10_retro_desc}

Why does my camera shoot HEVC but computer can't play it?

Computer lacks HEVC decoder - Windows 10/11 ship without HEVC codec by default due to licensing costs. Microsoft makes HEVC decoder available as paid extension ($0.99 "HEVC Video Extensions" from Microsoft Store) or free if device came with HEVC support bundled. Without codec, Windows Media Player and Photos app can't play HEVC files showing "codec not supported" error. VLC, MPV, and other third-party players include HEVC decoder freely - install alternative player or purchase Microsoft's extension.

macOS situation better - HEVC support built into macOS High Sierra (2017) and later. Macs play HEVC files natively in QuickTime, Safari, Photos. Older macOS versions (Sierra and earlier) lack HEVC - update OS or use VLC. Linux support through software decoders - VLC, MPV, FFmpeg handle HEVC on any Linux distribution. Hardware acceleration requires recent GPU drivers but software decoding works universally. Open-source world embraced HEVC despite patent issues; commercial OS vendors (Microsoft) require user-paid licenses.

Solutions ranked by preference: 1) Install VLC (free, works immediately, no system changes). 2) Purchase HEVC extension from Microsoft Store if using Windows apps. 3) Convert HEVC files to H.264 (time-consuming, quality loss, but universal compatibility). Don't repeatedly transcode - solve decoder availability once rather than converting library. Camera producing HEVC is fine; computer needs appropriate software to decode it. This isn't camera problem requiring camera setting change unless you specifically need H.264 for workflow requirements.

How does HDR video in HEVC work and what's required to preserve it?

HDR (High Dynamic Range) video requires three components: 10-bit color depth (Main 10 profile), HDR transfer function (PQ/HLG), and wide color gamut (BT.2020). HEVC supports HDR through metadata specifying these parameters. Standard workflow can accidentally strip HDR converting to SDR (Standard Dynamic Range). To preserve HDR during conversion: must maintain 10-bit encoding, copy HDR metadata (MaxCLL, MaxFALL, mastering display parameters), and specify appropriate transfer characteristics. Without all three, HDR display shows SDR image.

FFmpeg HDR preservation: `ffmpeg -i input_hdr.mp4 -c:v libx265 -crf 22 -pix_fmt yuv420p10le -x265-params hdr-opt=1:repeat-headers=1:colorprim=bt2020:transfer=smpte2084:colormatrix=bt2020nc:master-display=G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,50):max-cll=1000,400 -c:a copy output_hdr.mp4`. Complex parameters preserve HDR metadata. Use MediaInfo on source file to extract exact values for master-display and max-cll. Copying generic values can produce incorrect HDR rendering. For casual conversion, `-x265-params hdr-opt=1` maintains most HDR information automatically.

Playback requirements - HDR file needs HDR-capable display and HDR-aware player. Playing HDR file on SDR display shows washed-out or overly dark image because HDR tone curve isn't appropriate for SDR. Modern HDR TVs, phones, monitors display correctly; older displays can't. Player must recognize and process HDR metadata - VLC (version 3.0+), MPV, Plex, Kodi support HDR passthrough. Browser playback varies - some browsers tone-map HDR to SDR, others pass through on HDR displays. HDR is end-to-end technology requiring support at capture, encoding, distribution, and display. Breaking any link in chain loses HDR.

Should I convert my DVD/Blu-ray collection to HEVC for space savings?

DVDs (480p/576p MPEG-2) benefit moderately from HEVC conversion. Original DVD rip: 4-8GB (full disc) or 1-2GB (main movie, H.264 encode). HEVC re-encode: 700MB-1.2GB at similar quality. Space savings meaningful but DVD quality ceiling limits benefit - heavy compression reveals source's limitations (low resolution, MPEG-2 artifacts). Marginal value unless storage extremely constrained. Better approach: keep H.264 DVD rips (good balance), or if encoding fresh from discs use HEVC with conservative CRF (20-22) preserving maximum quality from limited source.

Blu-rays (1080p H.264) show stronger HEVC benefit. Original Blu-ray rip: 20-45GB (full disc), 8-15GB (main movie, remux). HEVC encode: 4-8GB at transparent quality. Reclaiming 5-10GB per movie is significant for large collections. 100-movie Blu-ray collection: 1-1.5TB (H.264 remuxes) versus 500-800GB (HEVC encodes), saving 500-700GB. Worthwhile if storage constrained or library large. Use CRF 20-22 for near-lossless quality, CRF 24-26 for transparent quality with smaller files. Test sample encodes before batch processing entire collection.

Considerations before converting: encoding time (weeks to months for large library), quality loss (transcoding always lossy even at high quality), storage cost versus time value (1TB drives are cheap), future format changes (might need to convert again to AV1/future codec). If storage isn't immediate constraint, keep H.264 sources. If storage is expensive (NAS, cloud storage with monthly fees), HEVC conversion has economic justification. Calculate: hours of encoding time × your hourly value versus cost of additional storage. Often buying larger drive is more cost-effective than spending weeks encoding. Do conversion if storage genuinely constrained or as learning project, not merely for compression's sake.

Can I losslessly extract HEVC stream from container without re-encoding?

Yes - remuxing changes container without touching codec stream. Extract HEVC from MP4 to raw HEVC: `ffmpeg -i video.mp4 -c:v copy -an output.hevc` copies video stream exactly without decode/encode (lossless, fast). Remux HEVC to different container: `ffmpeg -i video.mkv -c copy video.mp4` moves streams from MKV to MP4 container unchanged. Useful for container compatibility (device plays MP4 but not MKV), extracting elementary stream for analysis, or container-specific features (MKV chapters, MP4 iTunes tags).

Stream copy limitations - can only copy compatible streams. Not all containers support all codecs: HEVC in MP4 (requires newer MP4 standard), HEVC in MKV (fully supported), HEVC in AVI (technically possible but problematic). Audio/subtitle streams have similar compatibility. FFmpeg warns about incompatibilities: "Codec not currently supported in container" requires different container or transcoding. When remuxing fails, either choose different container or transcode streams causing issues (ideally keeping video intact, converting only audio/subs).

Quality verification - confirm remux truly lossless. Check file hashes (not matching because container changed but video stream should match): extract streams from both files, compare checksums. Or use frame-accurate comparison: extract frames from original and remuxed file: `ffmpeg -i original.mp4 -f framemd5 original.txt` and `ffmpeg -i remuxed.mp4 -f framemd5 remuxed.txt`, then `diff original.txt remuxed.txt` - should show identical frame hashes. This confirms pixel-perfect preservation. Stream copy is truly lossless if done correctly but good practice to verify for critical content.

What does HEVC's complicated adoption teach about codec standardization?

Patent licensing complexity kills adoption momentum - HEVC's technical excellence undermined by multiple patent pools (MPEG-LA, HEVC Advance, Velos Media) creating legal uncertainty and unpredictable costs. Companies hesitated deploying HEVC not knowing final licensing burden. H.264 had patent issues but single pool (MPEG-LA) with known reasonable fees. HEVC's fragmented licensing scared away potential adopters especially for web usage. This vacuum enabled royalty-free alternatives (VP9, AV1) gaining traction despite initially inferior compression. Lesson: legal clarity matters as much as technical performance for widespread adoption.

Hardware ecosystem determines real-world viability - HEVC succeeded in controlled environments (streaming services, Blu-ray, broadcast) where encoder and decoder coordinated. Failed for user-generated content and web video where encode/decode happens on arbitrary devices with varying support. H.264's decade of universal hardware support created network effects impossible for HEVC to overcome. Users recording in HEVC couldn't share confidently; platforms avoided HEVC due to client compatibility uncertainty. Codec standardization isn't enough - needs years of hardware deployment reaching critical mass before becoming practical interchange format.

Transitional formats face both directions' disadvantages - HEVC arrived after H.264 matured but before AV1's patent-free promise. Squeezed between incumbent with superior compatibility and future codec with licensing clarity. Formats succeeding long-term either dominate completely (H.264) or offer compelling differentiator (AV1's open licensing). Incremental improvements (HEVC's compression) without resolving predecessor's problems (patents) or offering new advantage (openness) create orphan formats. HEVC found niches (4K streaming, HEIF images, broadcasting) but never achieved H.264's universality or AV1's momentum. Design lesson: revolutionary change with clear benefits beats evolutionary improvement with legacy baggage.