Why iPhone Slow Motion Video Looks Wrong on PC
You transfer a slow-motion clip from your iPhone to your PC, drop it into your editor, and something is off. The slow motion plays at normal speed. Or the audio drifts out of sync. Or the clip stutters during playback. Or the editor refuses to import it at all.
This is one of the most common and least-understood problems in mobile-to-PC video workflows. It is not a transfer error. It is not a corrupt file. It is two specific technical characteristics of how iPhone records slow motion — and most PC editors are not built to handle either of them automatically.
Understanding both issues takes two minutes and makes every solution in this guide make sense immediately.
The Two Real Problems: VFR and HEVC
Problem 1: Variable Frame Rate (VFR)
When you record slow motion on iPhone and use the built-in Camera app to set where the slow-motion section starts and ends, the resulting file is a Variable Frame Rate video. It contains high-frame-rate footage (120fps or 240fps) in the slow sections and normal-speed footage (30fps) in the regular sections — all inside the same file.
This is elegant on iPhone. The Photos app and QuickTime understand it perfectly. On PC, most video editors expect Constant Frame Rate (CFR) — one consistent frame rate throughout the entire file. When a CFR-expecting editor encounters a VFR file, it misinterprets the timing data. The result: slow-motion sections play at the wrong speed, audio falls out of sync, or the editor drops frames trying to reconcile the mixed frame rates.
Which editors struggle with VFR:
- iMovie on Windows equivalent apps
- Vegas Pro (older versions)
- Most basic or consumer-grade editors
Which editors handle VFR natively:
- Adobe Premiere Pro (interprets VFR with some manual adjustment needed)
- DaVinci Resolve (handles VFR well with correct project settings)
- Final Cut Pro (native support — Mac only)
Problem 2: HEVC / H.265 Codec
iPhones from iPhone 8 onward record slow motion in H.265 (HEVC) by default at higher quality settings. H.265 delivers significantly better quality at smaller file sizes than H.264 — but requires hardware decoding support and, on Windows, the HEVC Video Extensions codec pack from the Microsoft Store.
Without the codec pack installed, Windows-based editors either refuse to import the file or import it with a black video track and audio only.
The combined effect: An iPhone slow-motion file can be simultaneously VFR and H.265 — meaning your PC editor may struggle with the codec, and even if it imports successfully, may still mishandle the variable frame rate timing. Fixing one without the other produces footage that still looks wrong.
Before You Convert: Check What You Are Working With
Knowing your file’s specs before converting saves time and prevents the wrong fix for the wrong problem.
How to check on Windows: Right-click the video file, select Properties > Details. This shows the codec and frame rate. For a definitive read, use MediaInfo, which shows whether the file is VFR or CFR under the Video track’s “Frame rate mode” field.
How to check on Mac: Open the file in QuickTime Player, go to Window > Show Movie Inspector. The codec and frame rate are listed. For VFR detection, use MediaInfo for Mac.
What you will typically find:
- iPhone 13 and later, slo-mo at 4K: H.265, VFR
- iPhone 13 and later, slo-mo at 1080p: H.265 or H.264, VFR
- iPhone 8 to 12, slo-mo: H.264, VFR
- Older iPhones: H.264, may be CFR depending on model and settings
Approach 1: Convert to CFR Before Editing (Recommended for Most Editors)
Converting VFR to CFR before importing into your editor is the cleanest, most universal fix. It works with every PC editor, eliminates sync drift, and bakes the slow-motion effect permanently into the output file at the correct playback speed.
The key is setting the output frame rate correctly — matching the high frame rate of the slow-motion section so the slow-motion effect is preserved at full fidelity.
Frame rate logic:
- iPhone 120fps slo-mo → export at 120fps CFR to preserve full slow-motion effect, or 30fps CFR if you want the slow motion pre-rendered at 4x speed reduction
- iPhone 240fps slo-mo → export at 240fps CFR to preserve full slow-motion, or 30fps CFR for 8x speed reduction pre-rendered
Exporting at the high frame rate gives your editor full control over speed ramping. Exporting at 30fps pre-renders the slow motion at a fixed speed — simpler, but less flexible for editing.
Using TotalMedia VideoConverter
TotalMedia VideoConverter handles MOV to MP4 conversion with custom frame rate settings on both Mac and Windows — making it straightforward to convert iPhone slo-mo footage to a CFR MP4 your PC editor handles cleanly.

Step-by-step:
- Open TotalMedia VideoConverter and click Converter in the left sidebar.
- Click + Add File/Folder and select your iPhone slow-motion MOV file or a folder of clips.
- In the right panel, select the Video tab and choose MP4 as the output format.
- Click the settings gear to open Custom Settings.
- Set the encoder to H.264 — universally compatible with all PC editors, no codec pack required.
- Set the resolution to match your source — 1920×1080 for 1080p slo-mo, 3840×2160 for 4K.
- Set the frame rate to your target:
- 120 if you want to preserve full 120fps slow-motion for speed control in your editor
- 240 if your source is 240fps and you want maximum slow-motion control
- 30 if you want the slow motion pre-rendered at normal playback speed
- Set bit rate to 20–30 Mbps for 1080p or 50–80 Mbps for 4K to preserve slow-motion detail.
- Save the configuration as a preset — for example, “iPhone Slo-Mo 120fps CFR” — for reuse across future projects.
- Set your output folder via Save to and click Convert All.
- Monitor real-time progress in the dashboard. Find converted files in the Finished tab when complete.
Using HandBrake (Free Alternative)
HandBrake converts iPhone slo-mo MOV files to H.264 MP4 effectively, but requires one important setting to handle VFR correctly.
- Open HandBrake and add your iPhone MOV file via Open Source.
- Under Output Settings, set format to MP4 and codec to H.264 (x264).
- Under Video, find the Framerate setting. This is the critical step:
- Change from Same as source to a fixed frame rate — either 30, 60, 120, or 240 depending on your intent.
- Select Constant Framerate in the option below the frame rate selector. This forces CFR output.
- Set Quality (RF) to 18–20 for near-lossless output.
- Under Audio, set codec to AAC at 192 kbps.
- Choose your output destination and click Start Encode.
Important: Do not leave HandBrake’s framerate on “Same as source” for VFR iPhone footage. This passes through the variable frame rate unchanged — your editor will still have the same sync and timing problems. Explicitly selecting a fixed frame rate and Constant Framerate mode is the fix.
Using FFmpeg (Command Line)
FFmpeg gives the most precise control over VFR-to-CFR conversion.
Convert iPhone slo-mo MOV to CFR MP4 at 120fps:
ffmpeg -i input.mov -vcodec libx264 -r 120 -vsync cfr -acodec aac -b:v 20000k -b:a 192k output.mp4
Convert to 30fps CFR with slow motion pre-rendered:
ffmpeg -i input.mov -vcodec libx264 -r 30 -vsync cfr -acodec aac -b:v 8000k -b:a 192k output.mp4
Breaking this down:
-r 120— sets output frame rate to 120fps-vsync cfr— forces constant frame rate output, eliminating VFR timing issues-b:v 20000k— sets video bit rate to 20 Mbps
Batch convert a folder of iPhone slo-mo clips:
for f in *.mov; do ffmpeg -i "$f" -vcodec libx264 -r 120 -vsync cfr -acodec aac "${f%.mov}.mp4"; done
Approach 2: Edit VFR Natively in Premiere Pro or DaVinci Resolve

If you use Adobe Premiere Pro or DaVinci Resolve, converting to CFR first is optional — both editors can work with VFR footage directly when set up correctly.
Adobe Premiere Pro
Premiere Pro accepts VFR footage but interprets it as CFR internally. To work with iPhone slo-mo correctly:
- Import the MOV file into your Premiere Pro project normally.
- Right-click the clip in the Project panel and select Modify > Interpret Footage.
- Under Frame Rate, select Assume this frame rate and enter the high frame rate of your clip — 120 for 120fps footage, 240 for 240fps.
- Click OK. Premiere now treats the clip as a high-frame-rate file.
- In the timeline, right-click the clip and select Speed/Duration. Set speed to a percentage that produces your intended slow-motion effect:
- 120fps clip on a 30fps timeline → set speed to 25% for 4x slow motion
- 240fps clip on a 30fps timeline → set speed to 12.5% for 8x slow motion
For H.265 iPhone footage on Windows: Install the HEVC Video Extensions from the Microsoft Store before importing. Without it, Premiere cannot decode H.265 on Windows systems without compatible hardware.
DaVinci Resolve
DaVinci Resolve handles iPhone slo-mo well when project settings match the source frame rate.
- Create a new project. Under Project Settings > Master Settings, set the timeline frame rate to match the high frame rate of your footage — 120fps or 240fps.
- Import your iPhone MOV file into the Media Pool.
- Right-click the clip and select Clip Attributes. Under Video, confirm the frame rate matches your source.
- Add the clip to the timeline. In the Inspector panel, find the Speed control and set it to the percentage that produces your intended slow-motion effect.
- Resolve renders the slow motion smoothly in a high-frame-rate timeline.
Note: DaVinci Resolve Free handles H.265 footage well on Mac. On Windows, H.265 decoding in Resolve Free depends on your GPU. Resolve Studio (paid) includes full software H.265 decoding on all hardware.
Fix for Windows: Installing HEVC Video Extensions
If your PC editor imports the iPhone MOV but shows a black video track, the H.265 codec is the culprit.
- Open the Microsoft Store on Windows 10 or 11.
- Search for HEVC Video Extensions.
- The official Microsoft version is a small paid download. A free alternative — HEVC Video Extensions from Device Manufacturer — is sometimes available depending on your system hardware.
- Install and restart your video editor.
- Try importing the iPhone MOV again.
This fix resolves the import black screen issue but does not fix VFR timing problems. If audio sync or playback speed is still wrong after installing HEVC extensions, apply the CFR conversion in Approach 1.
Transferring iPhone Slow Motion Footage to PC
Before converting, the file needs to be on your PC. iPhone slo-mo files are large — a one-minute 240fps clip can run 400MB–1GB depending on quality settings.
Via USB cable (fastest, most reliable):
- Connect iPhone to PC with a USB cable.
- Unlock your iPhone and tap Trust when prompted.
- Open File Explorer on Windows. Your iPhone appears under “This PC.”
- Navigate to Internal Storage > DCIM and copy the MOV files to your PC.
Via iCloud for Windows:
- Install iCloud for Windows from the Microsoft Store.
- Sign in with your Apple ID.
- Enable iCloud Photos — your iPhone photos and videos sync automatically to a folder on your PC.
- Note: iCloud may convert HEVC files to H.264 during transfer depending on your settings. Check iCloud Settings > Photos > Download and Keep Originals on your iPhone to prevent automatic conversion.
Via AirDrop to Mac, then transfer to PC: For users with both Mac and PC, AirDrop the file to Mac first, then move it to a shared folder or external drive for PC access.
Recommended Settings Summary
| Intent | Format | Codec | Frame Rate | Bit Rate |
|---|---|---|---|---|
| Full slo-mo control in editor (120fps) | MP4 | H.264 | 120fps CFR | 20–30 Mbps |
| Full slo-mo control in editor (240fps) | MP4 | H.264 | 240fps CFR | 30–50 Mbps |
| Pre-rendered slow motion at 4x | MP4 | H.264 | 30fps CFR | 8–12 Mbps |
| Pre-rendered slow motion at 8x | MP4 | H.264 | 30fps CFR | 8–12 Mbps |
| Native edit in Premiere / Resolve | MOV | H.265 or H.264 | VFR (unchanged) | Source |
Common iPhone Slow Motion PC Problems and Fixes
Clip imports but plays at normal speed: The editor is not interpreting the VFR timing correctly. Convert to CFR using TotalMedia VideoConverter or HandBrake, or use Interpret Footage in Premiere Pro to set the correct frame rate manually.
Audio is out of sync after transfer: Classic VFR symptom in a CFR-expecting editor. Convert to CFR before editing. Set a fixed frame rate in HandBrake or use the -vsync cfr flag in FFmpeg.
Black video track on import: H.265 codec is not installed on Windows. Install HEVC Video Extensions from the Microsoft Store and restart your editor. If the problem persists after installation, convert from H.265 to H.264 using TotalMedia VideoConverter.
Slow motion is choppy in the timeline: High-frame-rate footage (120fps, 240fps) is computationally demanding. Generate proxy media in your editor for smooth editing — use the original high-frame-rate file at export. In Premiere Pro: right-click the clip > Proxy > Create Proxies.
Converted clip has no slow motion — plays at full speed: The slow-motion effect was set inside the iPhone Photos app after recording, not baked into the file. Export the clip from the Photos app on iPhone (not just copied via File Explorer) to get a file with the slow-motion timing embedded. Alternatively, set the speed manually in your editor using the frame rate approach described in Approach 2.
FAQ
iPhone slow-motion footage has two characteristics that cause problems on PC. First, it uses Variable Frame Rate (VFR) encoding — mixing high-frame-rate slow-motion sections with normal-speed sections in the same file. Most PC editors expect Constant Frame Rate and misinterpret VFR timing, causing wrong playback speed and audio sync drift. Second, newer iPhones record in H.265, which requires the HEVC Video Extensions codec pack on Windows. Both issues need to be addressed for correct playback and editing.
Convert the MOV file to H.264 MP4 at the high frame rate of the slow-motion section — 120fps for 120fps footage, 240fps for 240fps footage — using a fixed Constant Frame Rate. TotalMedia VideoConverter handles this via Custom Settings: set encoder to H.264, frame rate to 120 or 240, and convert. The slow-motion effect is fully preserved in the output file at the correct frame rate for your PC editor to interpret.
Variable Frame Rate (VFR) means a video file contains footage at different frame rates within the same file. iPhone uses VFR for slow motion — recording the slow-motion sections at 120fps or 240fps and the normal sections at 30fps in a single clip. PC editors built around Constant Frame Rate cannot reconcile the mixed timing data, resulting in incorrect playback speed, dropped frames, and audio sync drift. Converting to CFR before editing eliminates these issues.
Premiere Pro can import iPhone VFR slow-motion footage, but requires manual interpretation. Right-click the clip in the Project panel, select Modify > Interpret Footage, and set the frame rate to match the high-frame-rate section of the clip (120 or 240fps). Then set the clip speed in the timeline to the correct percentage for your intended slow-motion effect. On Windows, the HEVC Video Extensions codec pack is also required for H.265 iPhone footage.
Audio sync drift in iPhone slow-motion footage on PC is almost always caused by Variable Frame Rate misinterpretation. Convert the file to Constant Frame Rate using TotalMedia VideoConverter, HandBrake with Constant Framerate mode enabled, or FFmpeg with the -vsync cfr flag. This eliminates the timing mismatch that causes sync drift.