How to make a loop on iPhone: a beginner's guide to looping
To make a loop on iPhone, set a tempo, record one to four bars after a count-in, stop exactly on the next downbeat, then overdub new layers while it repeats. Use wired headphones and a looper with latency compensation so the layers stay in time.
Updated: 2026-10-04 · ibigcall
What a loop actually is
A loop is a short piece of audio that repeats with no gap: one bar of a strummed chord, two bars of a beatbox groove, four bars of a bass line. A looper records that first piece, plays it back over and over, and lets you add more layers on top while it keeps cycling. Hardware loop stations such as the BOSS RC series work this way, and so do looper apps on the iPhone. The idea is the same; the iPhone simply replaces the footswitch with a button on the screen.
Two words come up constantly:
- Master loop - the first recording. Its length becomes the length everything else repeats to.
- Overdub - recording on top of a loop that is already playing, so the new layer is added to what is there instead of replacing it.
Step 1: decide what you are going to loop
Before you touch record, know exactly what the first loop will be and how long it is. Roland's beginner guide to its Loop Stations suggests starting with something as plain as one four-count bar of a G major chord. That advice holds on a phone too. A short, simple foundation is easier to cut cleanly, and every later layer depends on it.
Good first loops:
- A chord progression of 1, 2 or 4 bars.
- A simple beat: kick, snare, hi-hat - played on pads or beatboxed into the mic.
- A bass line that repeats every bar.
Step 2: set the tempo and turn on the count-in
The hardest part of looping is not the technology, it is timing the start and the end of the first take. If you press stop a fraction too late, the loop gets a small hiccup on every repeat; too early, and the last beat gets cut off. Two tools take most of the pain away:
- Metronome. Pick a tempo you can play comfortably and let the click run while you record.
- Count-in. The app plays one bar of clicks before recording starts, so you have time to get your hands on the instrument and come in on the downbeat.
Many looper apps also round the first take to a whole number of bars at the chosen tempo, which hides small timing slips at the end of the take.
Step 3: record the first loop
Count the bar out loud in your head - "1, 2, 3, 4" - and press record on the "1". Play your part. Press again on the next "1", the moment the bar ends. The loop starts playing straight back.
Listen to a few repeats before adding anything. If you hear a bump or a gap at the seam, record it again. It is much faster to redo a two-second loop than to fix it after five layers are stacked on top.
A tip from live loopers: let the last note ring through the seam rather than stopping it dead. A chord that decays into the first beat sounds natural; a chord that is choked just before the loop restarts sounds like a glitch.
Step 4: overdub the next layers
Now the loop is playing and you add parts on top. There are two common ways to do it:
- Overdub on the same track. Each pass is merged into the existing loop. Quick, but you cannot change the balance between layers later.
- Record each part on its own track. Every track has its own volume, pan and effects, so you can mix the drums down, mute the bass for a breakdown or delete one bad take without losing the rest. This is what a multitrack looper is for.
Build from the bottom up: rhythm first, then bass, then chords, then melody. Each new layer should leave room for the next one. If everything plays all the time, the loop turns to mush quickly.
Loop length multiples
Not every part has to be as long as the master loop. A drum loop can be one bar while the chord progression runs four. Loopers usually let later tracks be 1x, 2x or 4x the master loop so they stay in sync. When you plan a part that changes every bar, give it a longer track.
Step 5: understand latency and why it matters
Latency is the delay between something happening and the device processing or playing it. On an iPhone there are two parts. iOS reports them to apps as input latency (the delay for audio coming in) and output latency (the delay for audio going out), both measured in seconds.
Why this matters for looping: when you overdub, you hear the loop a few milliseconds after the phone plays it, and the phone receives your playing a few milliseconds after you play it. Without correction, every overdub lands slightly late. One layer late by 15-20 ms is barely noticeable; five layers each late by the same amount sound loose and flammy.
Latency compensation fixes this. The app knows the round-trip delay and shifts each recorded take back by that amount, so the take lands where you actually played it. It is the single most important feature to check in any looper app.
Wired is better than Bluetooth
Bluetooth headphones add a lot of delay. In Stephen Coyle's measurements, Bluetooth audio averaged around 224 ms against about 61 ms for wired audio in the same test. A delay that large makes it very hard to play in time with what you hear. For overdubbing, use wired headphones, a USB audio interface, or the iPhone speaker. Bluetooth is fine for listening back to finished loops.
When you record with the built-in microphone and the loop plays through the speaker, the mic picks up the speaker too. That is sometimes fine for a quick sketch, but headphones give cleaner layers.
Step 6: turn loops into a song
A loop on its own is a groove. A song needs change: an intro, a verse, a chorus, a breakdown. Ways to get there with a looper:
- Mute and unmute tracks to make sections - drums and bass alone for the verse, everything in for the chorus.
- Record a linear track that runs over the whole song for vocals or a solo, instead of looping it.
- Write the lyrics next to the loop while it plays, so words and music develop together.
- Export the result as audio to share, or as MIDI to keep working in a desktop DAW.
Common beginner mistakes
| Problem | Likely cause | Fix |
|---|---|---|
| Bump at the loop seam | Stop pressed early or late | Use a count-in and metronome, record again |
| Layers drift late | No latency compensation, or Bluetooth headphones | Turn compensation on, switch to wired |
| Loop sounds cluttered | Too many parts in the same range | Mute some tracks, leave space for the melody |
| Can't fix one bad layer | Everything overdubbed onto one track | Put each part on a separate track |
Doing it in iSimpleLoop
iSimpleLoop is a free looper for iPhone and iPad built around these steps. The first take sets the loop length, and an overdub stops itself after one lap. You get a count-in, a metronome and up to 8 tracks, each either looped or linear. Each track records from the microphone, the built-in guitar, keys and pads, or both. Latency compensation is built in, and the settings screen shows the measured input, output and round-trip latency of your setup. When the loop turns into a song, you can export WAV, M4A or MIDI. No account or subscription is needed, and it works offline.
Frequently asked questions
How long should my first loop be?
One, two or four bars is a good start. Short loops are easier to cut cleanly, and you can make later tracks 2x or 4x longer if a part needs more room.
What is overdubbing in a looper?
Overdubbing means recording on top of a loop that is already playing. The new layer is added to what is there instead of replacing it.
Why do my overdubs sound late?
Audio input and output each add a small delay. Without latency compensation, every layer lands a few milliseconds late, and Bluetooth headphones make it much worse.
Can I loop with just the iPhone microphone?
Yes. Headphones give cleaner layers, though, because with the speaker on, the mic also records the loop playing back.