Practical hardware guide

Scarlett on USB-C iPhone or iPad: separate power from data

Choose a supported Scarlett/mobile pairing and test the data port, separate supply or powered hub before troubleshooting app audio.

START HERE

Check the exact Scarlett model and mobile-device support first. Some USB-C iPhones/iPads cannot power an interface directly. On supported Scarlett models with a separate 5 V DC input, that port supplies power while the port marked USB carries the mobile data connection.

A stable external-audio recording on the mobile app, with the source and battery behavior verified.

In this guide
Before you start
  • An officially supported Scarlett model, current compatible firmware and a supported iOS/iPadOS version.
  • The appropriate USB data cable and any documented external-power arrangement.

Before you change the setup

A USB-C mobile device can connect to an audio interface without necessarily supplying all the power it needs. Focusrite's guidance distinguishes direct connections, models with a dedicated 5 V DC input and powered-hub arrangements. The correct choice depends on the exact interface and phone/tablet, not simply on both having USB-C sockets.

Start with the manufacturer's supported-device list and firmware guidance. An interface expected to work is not the same category as one explicitly supported. For a recording you cannot repeat, keep that distinction visible in the setup notes and rehearse the complete mobile application workflow.

Run a controlled check

  1. Verify the pairing

    Identify the Scarlett model/generation and the mobile device/OS version. Check Focusrite's current support list and perform any documented firmware preparation on a supported computer before the mobile session.

    Look for: The proposed pairing has a documented basis rather than an assumption about class-compliant USB audio.

  2. Separate the ports by function

    Locate the interface port marked USB and, if present on a supported model, the separate 5 V DC input. Connect mobile data to the USB port and use the documented supply arrangement when direct bus power is insufficient.

    Look for: The interface has both the required data path and a suitable power source.

  3. Check power and detection

    Observe the interface's connection indication and whether the mobile app detects external audio. If a powered hub is required, follow the manufacturer's topology and check its power input rather than inserting random adapters.

    Look for: A stable detected interface is established before microphone gain or software effects are adjusted.

  4. Allow the intended audio input

    In the recording app, select or verify the external input where supported and check the app's microphone permission. On iOS/iPadOS that permission also applies to an external interface. Record a short phrase and replay it.

    Look for: The saved recording uses the intended external microphone instead of silently falling back to the phone's built-in mic.

  5. Rehearse the full power arrangement

    Run the intended app for a representative session and inspect both interface stability and phone/tablet battery behavior. Test normal screen locking or interruptions only where the app's workflow supports them.

    Look for: The setup's practical battery and connection limits are known before a longer take.

Read the result and keep a working setup

If the interface repeatedly reconnects, investigate power and the USB path before increasing gain. If it remains detected but the app records silence, check input selection, microphone permission and channel handling. If another app works with the same connection, the remaining issue is more likely application-specific than a general interface failure.

A separate interface power supply does not automatically mean the phone is charging. Focusrite distinguishes that arrangement from a compatible powered hub that can also supply the mobile device. Verify the battery indicator and the complete topology rather than judging by the number of connected cables.

Use a short spoken test identifying the external microphone and gently vary its distance to confirm which source is recorded. Keep listening levels comfortable and do not tap the capsule as a diagnostic. Save the successful app, cable, power and input-channel combination in a note.

No mobile runtime or multi-channel app compatibility is promised here. The finished result is a playable test file and a stable rehearsal with your exact pairing. That evidence is more useful than a generic claim that any USB-C interface works with any USB-C phone.

Keep these distinctions clear

Keep these distinctions clear
SymptomFirst check
Connection cycles or power indicator abnormalSupported power arrangement and data cable.
Detected but no recorded inputApp permission, input and channel selection.
Interface stable; phone battery fallsWhether the topology also supplies the mobile device.
Only one app failsThat app's external-audio support.

Try it on your own setup

Start small: try the free files or continue with a guide for the part you’re working on.

USB vs XLR for Streaming: What Does Your Setup Need? ↗

Sources & references

Documentation review checked 4 November 2026 using the primary sources listed below. This is not a hands-on product test: the diagnostic sequence and rehearsal suggestions are Foxdip editorial guidance. No measured performance, search volume, price or universal compatibility result is claimed.

  1. Focusrite — Bus-powered interface to iPhone/iPad ↗Checked 2026-11-04
  2. Focusrite — iPhone/iPad connection troubleshooting ↗Checked 2026-11-04
  3. Focusrite — Sound issues on iOS and iPadOS ↗Checked 2026-11-04

Spotted something out of date? Let Alex know.

How we put our guides together ↗
READ NEXT

A few places to go from here.

All stories

USB vs XLR for Streaming: What Does Your Setup Need?

Decide whether to keep your microphone, choose USB or build an XLR setup by tracing the connections, controls and extra gear you need.

USB Hub for a Mic, Webcam and Capture Card: What Works

Plugging a mic, webcam and capture card into one hub? Check speed and power separately, keep direct ports for devices that need them, then pick a hub.