iPhone Cinematic Mode Files: Editing the Depth Data Without Losing Bokeh
iPhone's Cinematic Mode records depth metadata that lets you change focus after recording. Here's how to export, edit, and convert without flattening the depth effect.
Marcus Rivera·May 8, 2026·8 min read
What Cinematic Mode Actually Captures
Apple's Cinematic Mode (iPhone 13+) records two pieces of data per frame:
The video frame itself (HEVC at 1080p30 on iPhone 13/14, 4K30 on iPhone 15+)
A depth map (per-pixel distance information from the camera)
The depth map allows post-production focus pulling: you can change which subject is in focus after the recording, just like adjusting focus on a video camera. Apple processes this in the Photos app and Final Cut Pro.
The catch: most third-party tools and conversions strip the depth data, leaving you with a video that has hardcoded focus blur (or no blur at all). If you want to edit Cinematic Mode footage with post-production focus control, the workflow has specific requirements.
This post covers the depth-preserving workflow, the export options that flatten it (intentionally or accidentally), and how to deliver Cinematic-style footage to platforms that don't support depth metadata. Our video compressor handles the final encoding step.
When the iPhone's Photos app plays the file, it dynamically applies the depth-based blur. The "video" you see is real-time composited from the source frames + depth map.
When you export from Photos or share via Messages, by default the depth is baked in. The recipient gets a regular video with the focus you chose at the time of export.
Preserving Depth on Export
To keep the depth track intact:
From Photos app on iPhone:
Select the Cinematic clip
Tap Share > Save to Files (NOT "Save Video")
The .mov file in Files retains the depth track
From Photos app on Mac:
Select clip
File > Export > Export Original
The .mov on disk has all tracks
Direct from iPhone via cable:
Connect iPhone to Mac via USB
Use Image Capture (or finder) to copy
Files transferred this way preserve all metadata
Avoid these:
AirDrop with default settings (re-encodes as flat video)
Email/iMessage (always flattens)
Cloud Photos download on Windows (strips depth)
Editing in Final Cut Pro
FCP 10.6 and later natively support Cinematic Mode editing:
Import the .mov file (with depth track intact)
Drag to timeline
Inspector > Cinematic Effect
Set focus points by clicking on subjects in the viewer
Adjust focus transitions with keyframes
The depth-based focus is computed at render time. You can change it at any point in editing without re-importing.
Editing in Premiere
Premiere does not support Cinematic Mode depth tracks as of 2026. Workarounds:
Option 1: Edit in FCP first
Apply focus decisions in FCP, export to ProRes 422 HQ. Import to Premiere as a regular flat video. Lose the ability to change focus after import.
Option 2: Use iPhone Photos app for focus, FCP/Premiere for editing
In Photos: tap Edit > set focus > Done. The clip's focus baked in. Export to flat video. Edit in any tool.
Option 3: Python pipeline (advanced)
Apple's APIs for reading depth tracks aren't open. There are some open-source tools (LumeCine on GitHub) for accessing depth data, but they're hobbyist quality and break with iOS updates.
For most non-FCP users, Option 1 or 2 is the realistic path.
Resolution and Codec Considerations
iPhone Model
Max Cinematic Resolution
Codec
iPhone 13 / 13 Pro
1080p30
HEVC 8-bit
iPhone 14 / 14 Pro
4K30
HEVC 10-bit (Pro models)
iPhone 15 / 15 Pro
4K30
HEVC 10-bit (Pro), Dolby Vision (Pro)
iPhone 16 / 16 Pro
4K30, 4K60 (Pro)
HEVC 10-bit, Dolby Vision (Pro)
Higher iPhone models record higher quality. The depth processing also improved between generations; iPhone 15 Pro's depth maps are noticeably more accurate than iPhone 13's.
For HDR Cinematic source (iPhone 14 Pro+), the workflow is more complex. See HDR10 vs Dolby Vision Conversion for the underlying HDR-to-SDR pipeline.
Exporting for Different Targets
After editing in FCP, export targets:
Target
Codec
Bitrate (4K)
Notes
YouTube
H.264
35 Mbps
YouTube re-encodes anyway
Vimeo Pro
H.264 / HEVC
50 Mbps
High quality acceptance
TikTok
H.264
22 Mbps
See platform export specs
Instagram
H.264
16 Mbps
1080p re-encoded
Master
ProRes 422 HQ
~880 Mbps
Pristine archival
The depth blur is permanent in any of these exports. Once flattened to a regular video, the focus can't be changed.
Blur looks unnatural at depth boundaries: depth map's edges aren't pixel-perfect. iPhone 13 has more visible boundary artifacts than newer models. Mitigation: feather the focus transition, avoid extreme background blur.
Depth tracking loses subjects in motion: fast-moving subjects can confuse the depth algorithm. Manually keyframe focus to follow the subject in FCP.
Aspect ratio looks weird: Cinematic Mode is designed for vertical content with subjects centered. Cropping to 16:9 or other aspect ratios reveals the depth boundary artifacts that vertical 9:16 format hides.
Focus changes feel jerky: focus transitions are sharp by default. In FCP, smooth them with keyframe interpolation set to "Ease In/Out."
Pro Tip: When recording Cinematic Mode, tap on subjects to set initial focus. The iPhone's algorithm uses this hint when computing the depth map. Auto-detected focus is less reliable.
Cinematic Mode vs Real Cinema Bokeh
Cinematic Mode simulates shallow depth-of-field with a depth map and Gaussian blur. Real cinema cameras (RED, ARRI, Sony FX9) achieve shallow DOF with large sensors and fast lenses.
Highlight bloom: Real lenses produce specular highlights with characteristic flare. Cinematic Mode renders flat blurs without these specular characteristics.
Edge transitions: Real DOF has gradual transition from in-focus to out-of-focus. Cinematic Mode has sharper transitions where the depth boundary is.
For social media content, Cinematic Mode's simulation is convincing. For professional filmmaking, the real thing still wins.
Storage Considerations
Cinematic Mode files are larger than regular video due to the depth track:
Resolution
Cinematic file size (1 minute)
Regular video file size (1 minute)
1080p30 (iPhone 13)
~150 MB
~85 MB
4K30 (iPhone 14 Pro)
~280 MB
~180 MB
4K30 Dolby Vision (iPhone 15 Pro)
~310 MB
~230 MB
About 70% larger. The depth track adds significant storage but provides post-production flexibility.
For backup workflow: keep Cinematic source files separately from regular videos. The Cinematic version is the editable master; flattened exports are derivatives.
Frequently Asked Questions
Can I add Cinematic Mode effect to non-Cinematic videos?
No. The effect requires the depth map, which is captured at recording time. Existing flat videos can't be retroactively converted. Tools like Topaz Video AI can simulate depth effects but at much lower quality.
Why does my exported video have flat focus when I had focus pulls in Photos?
Photos app's "Save Video" option flattens. Use "Save to Files" instead, then import the file into FCP for proper depth-aware editing.
Can I edit Cinematic Mode in DaVinci Resolve?
Limited. DaVinci doesn't natively understand Cinematic depth tracks. You can edit the flattened video, but post-production focus changes aren't possible. FCP is the practical Cinematic-aware NLE.
What about iPhone Action Mode video?
Action Mode is different (heavy stabilization for high-motion content). It doesn't have depth metadata and doesn't share the Cinematic Mode workflow.
Can I convert iPhone Cinematic to a regular MP4 while preserving the chosen focus?
Yes. Edit in FCP or Photos, set focus, then export to MP4 from Photos. The output is a regular video with the focus baked in. Use our HEVC to H.264 converter if needed for compatibility.
Does Apple Vision Pro support Cinematic Mode?
Vision Pro plays Cinematic videos with the depth effect. Specifically: the Photos app on visionOS displays them with proper depth. AirPlay or Sharing to Vision Pro preserves the depth track.
For iPhone Cinematic Mode editing: transfer files via Files or Image Capture (not AirDrop or Messages), edit in Final Cut Pro for post-production focus control, export to ProRes for archival or H.264 for delivery. Other NLEs lose the depth track on import. Our video compressor handles the final delivery encoding step after FCP export.
