Identify which sound is missing before repeating an iPhone screen recording. Your spoken commentary, sound from the displayed app, and the playback route are different things. Test a short saved recording with authorized material; hearing sound while making a recording does not prove that the resulting file contains it.
Name the intended audio source
Write down whether the tutorial needs your live voice, permitted app sound, or both. Check the saved recording in Photos before sending it to another editor. If it contains the intended voice there but appears silent elsewhere, investigate that playback or transfer separately. Do not change capture settings to fix a problem that first appears after delivery.
Apple's September 2026 screen-recording instructions describe opening Control Center, holding the recording control and enabling Microphone for recording with audio. Apple also warns that some apps may prevent audio or video recording, and screen recording cannot run simultaneously with screen mirroring. Those limits are not a promise that every app soundtrack will be captured.
Make two brief, clearly named tests
Use a screen and sound that you are entitled to record. In the recording controls, inspect the Microphone setting rather than assuming its previous state. Make a brief commentary test with it enabled: say a recognizable sentence, stop the recording, then play the saved file. Avoid recording a whole lesson until that sentence is present and understandable.
When permitted app sound is also required, make another short test in the actual app and compare the saved result. Keep each test separate so a changed microphone state cannot be mistaken for a changed app policy. Use an appropriate listening route and avoid placing private notifications or unrelated conversation in the test. Do not treat room sound picked up by the microphone as proof of direct app-audio capture.
A hypothetical phone tutorial
Suppose a creator hears music during a screen demonstration but later finds that their explanation is absent from the saved file. A ten-second voice test helps determine whether the intended commentary was recorded. A separate app test checks whether the required soundtrack is present in this specific capture.
If commentary works but an app prevents capture, the creator uses an authorized supported source or records a separate approved narration. Turning up speakers, repeatedly pressing the recording button or exporting the silent clip again does not establish that the app permits capture. This is a hypothetical workflow, not a measured recording failure or a workaround for an app restriction.
Preserve evidence through the edit
Keep the two test files and the successful original recording. Note the device, system version, app, microphone state and which sounds were actually heard in each saved file. Once the source is accepted, label any separately recorded narration so an editor does not mistake it for the phone's original captured audio.
Accept when the delivered recording contains the agreed sounds and speech can be understood through the actual beginning, middle and ending. Reject a voice heard only during capture, an unverified assumption about app audio, or a finished edit whose missing source sound is concealed by new music. Imagild can use an approved film brief or source recording, but this device-level capture check is external; generation cannot certify what the phone recorded.