Turn iPhone footage into reliable 24p or 30p files

An iPhone can record 24, 25, 30, 50 or 60 frames per second, and some clips use variable frame timing. Renaming a file or changing its metadata does not alter the images already captured. Converting different iPhone frame rates to standard 24p or 30p requires source inspection, a clear motion-handling choice, transcoding and playback checks.

Twenty-four progressive frames per second gives footage a cinema-associated cadence, while 30p captures more motion detail for online video, interviews and fast everyday action. Choose from the source recording and delivery platform rather than the phone model alone. The aim is a file with the intended timing, natural movement and audio that stays in sync.

Read the source frame rate

First, inspect each clip instead of inferring its settings from a filename. Labels such as 1080p, 4K or Cinematic describe resolution or a capture mode, not always the output cadence. Use QuickTime on a Mac, a suitable file inspector on Windows, or MediaInfo, and note the frame rate, codec, duration and pixel dimensions before editing.

The “p” means progressive: every frame is a complete image. Most iPhone video is progressive, including footage described as 24p, 30p, 50p or 60p. Australia inherited 50 Hz television and PAL broadcasting, so 25p and 50p remain familiar in local production histories. Many current streaming workflows use 24p for drama or 30p for general online delivery.

Prepare clips and inspect timing

Keep the originals untouched, especially in iCloud Photos or on the phone itself. Copy each required clip to the editing drive, give it a clear name and record its source rate in a shot list or edit-decision list. A second copy protects a paid shoot from accidental replacement during a long export.

Do not assume every file uses constant-frame-rate video. Depending on the iPhone model, iOS release, codec and capture app, a clip may vary its timing to save space or simplify encoding. A media analyser can report this property. If it is variable, frame sampling, blending or optical-flow processing may behave differently from constant-rate footage, so inspect motion around cuts and fast pans.

Decide where final conversion will occur. Editing at the source rate and exporting once is usually cleaner than converting every assembly before an effects pass. Log or Dolby HDR iPhone footage needs the appropriate colour-management transform first; changing 30p to 24p cannot repair an unsuitable tone curve or blown highlights.

Create a clean 24p master

For a 24p master, select exactly 24 fps and constant frame rate in the converter’s video settings. MP4 or MOV with H.264 gives broad playback support; H.265 creates smaller files when the destination accepts them. Retain the source resolution unless a delivery specification requires otherwise, mark the scan as progressive, and use a sensible quality or variable-bitrate setting rather than an aggressive fixed rate.

Do not merely relabel 30p footage as 24p. That trick can stretch or compress timing, send audio out of sync, or leave the player guessing how to construct frames. Transcoding produces real 24 fps frames, while retiming determines whether they represent dropped, blended, duplicated or newly synthesised images.

If the subject is travel, hospitality or gaming content, relevant local background can make the finished piece feel grounded. A feature on Australian casino entertainment, for example, may suit a measured 24p treatment. Slow, detailed motion works well for establishing shots, while rapid handheld movement may reveal cadence changes after processing.

Build a 30p delivery file

Choose 30p when the source already contains smooth 30 fps movement and the destination values compatibility or extra temporal detail. A native 30p file carries 25 per cent more frames each second than 24p, which helps fast pans, pets, children and handheld footage. The trade-off is a slightly less film-associated cadence and larger files at the same resolution and quality target.

Older hardware can limit capture choices because of processor speed, storage or thermal behaviour. An older iPhone comparison provides hardware-era context for an iPhone 6 Plus or similar device, although the exact model and installed iOS version offer the reliable answer.

Australian creators commonly prepare short clips for mobile-first social feeds, making 30p practical for phone viewing and mainstream platforms. Upload conditions still vary: fixed NBN service in parts of Sydney, Melbourne, Brisbane and Perth may behave very differently from a mobile connection or a slower regional service. Export a short test before committing a large batch.

Choose the right retiming method

Rate conversion and motion retiming are related but separate. To keep real-time duration, a 24p-to-30p job must represent 24 original frames across 30 output intervals; a 30p-to-24p job must compress 30 intervals into 24. Simple conversion drops or repeats frames, creating a mechanical pulse. Blending softens that pulse, while optical flow estimates intermediate frames and can create warping around hands, wheels or fast contrast edges.

Australian sports footage provides a useful example. An AFL or rugby clip recorded at 50p can appear smoother at 30p after careful retiming, yet heavy frame removal may make a ball or limbs jump. For 25p archival material, maintaining the same real-time duration on a 24p timeline generally requires a small timing adjustment; simply changing the number in the file header is unsafe.

High-frame-rate clips from iPhone Slow-Mo need their intended playback speed chosen before conversion. A 120 fps recording played at one-quarter speed becomes 30p, for example, while 240 fps can feed 30p at one-eighth speed if the intended result remains slow motion. Always retime the audio alongside the picture, and check whether the software letterboxes, trims or repeats frames to fill a new frame duration.

Run the conversion on Windows or Mac

Pavtube provides a Windows and Mac route for loading clips, choosing a target format and creating compressed video or audio output. Set 24 or 30 fps, enable constant frame timing if the interface offers it, select a progressive MP4 profile, then adjust resolution and bitrate before starting. Preview the result and retain the untouched phone file beside the converted version.

iMovie works for a simple 24p or 30p project because its project frame rate is set before the final share; existing variable-rate footage may still need preparation. Premiere Pro gives finer control through sequence settings, interpretation and retiming, including optical-flow options on supported hardware. In either program, avoid exporting, reimporting and converting the same timeline several times, since each generation loses quality.

Delivery settings matter after the desktop export. An Australian streaming project must account for over-the-top media delivery, because a service may transcode the uploaded file again and alter its cadence or bitrate. Coordinate Sydney, Melbourne, Brisbane and Perth release schedules with daylight-saving changes, and test playback through the actual app rather than trusting a desktop preview.

Check, export, and archive

Check the finished file frame by frame around cuts, whip pans and flashes. Its frame rate should be fixed at the chosen rate, duration should match the edit, and audio should remain aligned at the first and last spoken word. Watch it on an iPhone, a television and headphones; compression artefacts, duplicated motion and colour shifts can appear on only one of those paths.

Use progressive scan, AAC audio at 48 kHz, and a stereo bitrate around 320 kb/s unless the platform specifies otherwise. Archive the original iPhone clip, the project and a documented 24p or 30p export so future edits can start from the best source. The finished file should retain its intended cadence, preserve natural motion and play consistently across Australian phones, televisions and streaming apps.