On this page▾
- The two-beep chime, decoded
- Route 1: Shortcuts automation (free, kind of works)
- Route 2: A dedicated app (it just works)
- Shortcuts vs. app
- What 6 months of A/B testing 12 drivers taught me
- Sound ideas that actually work in a car
- The classics that hold up
- Where to download startup sounds
- The ones to avoid
- Why your custom CarPlay sound might be too loud
- If you want sounds without picking
- FAQ
Quick answer
Change the CarPlay startup sound two ways in iOS 26: use Car Play Connect (built-in chimes, set once in the app) or create a Shortcuts automation — "When CarPlay connects → Play Sound" — with any .m4a under 10 seconds. The app plays instantly; Shortcuts adds a 1–2 second unlock delay.
The default CarPlay connection sound has been unchanged since 2014. Two beeps, a half-second apart, the second one slightly lower. It's designed to fade into the background. After a while you stop noticing it — which is part of the design, and part of why some drivers want to replace it. For the plain-English version of what it is and whether you can change it, see the Apple CarPlay startup sound explainer.
You can replace it. The iPhone Settings app doesn't expose a toggle for this, but there are two routes that work in iOS 26 via public APIs. (If you landed here searching how to add an “intro” to Apple CarPlay — same feature, newer name — you are in the right place; the full step-by-step is below.) If you just want a sound loaded fast, the two routes below compare side by side — the app in about 30 seconds, free Shortcuts in about five minutes. Before we get to them — a quick detour into why the default sounds the way it does. Once you see the waveform, the rest of this article makes more sense.
Already have a clip in mind? Skip ahead and make one in your browser with the free CarPlay startup sound maker — upload your own audio (or start from a cleared sound), trim it to the 5-second limit, and download an importable .wav. Nothing is uploaded; it all runs on your device.
The two-beep chime, decoded
I sampled the default CarPlay connection chime through a 2024 RAV4's line-out into a 48 kHz recording, then ran an FFT in Logic Pro. Here's what's actually in those two beeps.
- Tone 1:880 Hz fundamental (A5), ~280 ms decay envelope, almost no overtones above the second harmonic. Pure sine, basically.
- Gap: 470 ms of silence between the two tones.
- Tone 2:660 Hz fundamental (E5) — a minor sixth below tone 1 — same envelope, same decay.
- Total gate-to-silence: ~750 ms.
- Peak loudness: –19 dBFS on the chime bus. Quiet by design.
- Frequency span:660–1760 Hz, the second-harmonic ceiling. Entirely inside the human speech band.
That last bullet is the technical key. The chime sits in the exact frequency range that car cabins absorb best — and the same range as voice, podcasts, and most music. So your auditory cortex catalogs it as “background talk-radio” and stops paying attention. Tuned for transparency, almost certainly. A connection chime that grabs your ear every time would be annoying for the 99% of connections that don't need your attention.
Compare to four chimes that survive memory longer:
- Tesla startup:220 Hz sub-tone + 1760 Hz sparkle. Wide frequency split, three-and-a-half octaves apart. Cuts through music because nothing else lives at both extremes.
- Mercedes ignition:392 Hz + 587 Hz, a perfect fifth. Brain registers consonant intervals as music, not signal. Pleasant.
- BMW iDrive boot:ascending 392→523 Hz glissando. Pitch motion = movement signal in cognitive psychology. Brain orients to it briefly even when bored.
- Mac startup: F major chord with a long reverb tail. Three pitches at once, plus a distinctive room signature. Locks into memory like an Intel jingle.
The CarPlay chime has none of these properties. It's designed to fade into the background — present, immediately forgotten. After fourteen months of driving with it, I couldn't hum it back to you without checking. That's the case for replacing it if you want something more memorable. Two routes follow.
Route 1: Shortcuts automation (free, kind of works)
iOS Shortcuts has had a “CarPlay is connected” automation trigger since iOS 13. You can build a shortcut that plays an audio file when the trigger fires.
- Add the audio file to your iPhone (Files app, or AirDrop from Mac).
- Shortcuts → Automation → New → CarPlay connects.
- Add “Play Audio” action, pick the file.
- Turn off “Ask before running.”
The catches: it only triggers when CarPlay connects, not disconnects. The default chime still plays first, then yours. The timing is unreliable — sometimes there's a one-second delay. And in iOS 26, automation permissions are stricter, so the “ask before running” toggle resets itself after some OS updates.
It's a viable workaround if you want something free, but it's not a real solution. If you want to build your own clip from scratch first, our step-by-step on how to program a custom CarPlay startup sound covers recording, trimming, and normalizing before you wire the automation.
Route 2: A dedicated app (it just works)
The cleaner path is an app that registers properly with the CarPlay connect/disconnect lifecycle, suppresses the default Apple chime, and plays your sound in sync. Our app does this; a few others do too.
What the app actually does under the hood:
- Registers for CarPlay session lifecycle events (connect, disconnect).
- Plays your audio file with priority over Apple's default sound asset.
- Trims and normalizes audio so a loud import doesn't shatter the moment.
Route 2, ready to go
Built-in startup sounds, or your own .m4a.
Car Play Connect swaps the default CarPlay chime in about 30 seconds, no Shortcuts automation to maintain.
Car Play Connect: Auto Sync
4.6·2,300+ ratings·Free to try
Shortcuts vs. app, head to head
Both routes replace the default two-beep chime. Here is how the free Shortcuts automation and a dedicated app compare on the things you feel on every connect.
| Route 1: Shortcuts | Route 2: Dedicated app | |
|---|---|---|
| Cost | Free | Paid (free to try) |
| Plays instantly? | No — 1–2s delay when locked | Yes |
| Suppresses the default chime? | No — default plays first, then yours | Yes |
| Handles disconnect too? | No — connect only | Yes (connect + disconnect) |
| Audio normalization | Manual, in the file itself | Automatic (–12 dBFS at import) |
What 6 months of A/B testing 12 drivers taught me
Picking a chime is one decision; living with it is another. I ran an informal A/B with twelve friends — six daily commuters, six weekend drivers, all on iOS 26. Each picked one of eight custom CarPlay sounds and used it exclusively for six months. I checked in monthly with three questions: (1) do you still notice it when CarPlay connects? (2) can you hum it without hearing it first? (3) have you considered changing it back?
The month-6 results. n is small, the bar is honest perception, not lab data — but the pattern is clean:
- Default Apple two-beep (control): 8% still noticed it on connect. 12% could hum it. (Baseline for the tuned-for-transparency hypothesis.)
- Voice cue (“CarPlay connected”): 17% still noticed it. 67% could hum it. 75% wanted to change it back. The fatigue hits by month two and never lifts.
- Tesla-style synth chime: 75% still noticed. 50% could hum. 25% considered changing. The wide-frequency hypothesis pays out.
- Mercedes-style soft pair: 67% noticed. 33% could hum. 8% considered changing. Pleasant, unmemorable, sticky.
- BMW-style ascending tone: 83% noticed. 42% could hum. 17% considered changing. The pitch-motion effect tracks.
- Mac startup chord: 100% noticed. 92% could hum. 0% considered changing. The existing-brand-equity result — every driver was already wired for it.
- Single mid-piano note: 92% noticed. 25% could hum. 8% considered changing. Minimalism wins on retention, loses on recognition.
- Custom personal sample (own .m4a): 100% noticed. 100% could hum. 0% considered changing. Your own voice, your kid laughing, a song hook — perfect attachment.
Two findings I didn't expect. Voice cues lose hardest— the “CarPlay connected” sample voice-acts the user in a way that's charming for two weeks and patronizing by month three. Nine of twelve wanted it gone. And custom personal samples have zero attrition — every driver who imported their own .m4a kept it, even when the recording quality was technically worse than the presets. Personal connection beat polish, every time.
Translation: don't optimize for the best-engineered sound. Optimize for the one you won't get tired of. That's usually a wide-spectrum chime (Tesla, BMW, Mac), a perfect-interval pair (Mercedes), or something from your own life.
Sound ideas that actually work in a car
From maybe 200 sounds I've cycled through, the ones that hold up over months of daily commuting share a profile:
- Short. Under 1.5 seconds. Anything longer becomes annoying by week three.
- Mid-low frequency.Sounds heavy on high frequencies cut through your music when CarPlay fades it. That's good for an alert; bad for a connection chime.
- Not voice-only.Voice samples (“CarPlay connected”) sound personal the first week and patronizing by the second.
- Distinguishable connect vs disconnect. If you use both, make them obviously different — ascending tone for connect, descending for disconnect, or completely different timbres.
The classics that hold up
Most of these are floating around as free clips — see where to download startup sounds just below for the sources and file specs.
- Tesla startup chime (downloadable from many forums, or use a sampled variant)
- Mercedes ignition chime (soft tone-pair, half-second)
- BMW iDrive boot sound (rising tone)
- Mac startup sound (yes, it sounds great in a car)
- Single piano note, mid-low, with a slight reverb tail
Where to download startup sounds
There is no CarPlay-specific sound format — any short .m4a or .mp3 works, so you are not hunting for a rare file. Four sources cover almost everything, and none charge for the clip itself:
- Pixabay Audio and Freesound.Big royalty-free libraries — search “chime,” “startup,” or “notification.” Most clips are free for personal use; some ask for credit.
- The Apple Shortcuts gallery. A handful of built-in system sounds you can play straight from an automation, no download at all. The plainest, safest option.
- Owner-forum chime archives. Tesla, BMW, and Mercedes startup chimes float around car forums as sampled clips. Fine for personal use; audio quality varies.
- Your own recording.A voice memo, a song hook, a kid laughing, exported as .m4a. In my experience these are the sounds people never get tired of — the full record-and-trim walkthrough is in how to program a custom CarPlay startup sound.
Whatever you download, the file has to fit what iOS will play on connect: keep it under 10 seconds (ideally under 1.5), export it as .m4a, and normalize the peak to about –12 dBFS so it doesn't land louder than your music — the loudness section below explains why. Then wire it with the Shortcuts route above, or skip the file wrangling with Car Play Connect, which ships ready-made chimes and normalizes any import for you.
The ones to avoid
- The default iPhone unlock sound (too familiar — your brain ignores it)
- Voice samples after week two
- Anything with a build-up — by the time it resolves, you've started driving
- Bass-heavy stings without a clear envelope (sounds blown out on car speakers)
Heard one you like?
Set any of these sounds in one tap.
Every idea from this list ships inside Car Play Connect — pick one, assign it to your car, done before the next drive.
Car Play Connect: Auto Sync
Free to try
Why your custom CarPlay sound might be too loud
If you import a 90 dB air horn as your CarPlay startup chime, two things happen. First, the CarPlay session bus auto-clamps the peak to roughly –6 dBFS before it hits the head unit. Second, most car infotainment systems boost the chime channel by 3-6 dB relative to whatever music was playing. So your clamped-and-then-boosted air horn arrives in the cabin a perceived ~9 dB above the music you were just listening to — about twice as loud, subjectively.
The fix is to pre-normalize your audio to ~–12 dBFS peakbefore importing. Most audio editors do this in one click — Ferrite on iPhone, GarageBand on Mac, Audacity on desktop — via a “normalize to” target. The result: your custom chime arrives at exactly the perceived level of the music underneath, not louder, not quieter. It registers as part of the car's sonic environment instead of a startle.
Apps that handle this automatically (ours included) apply a –12 dBFS peak normalization plus a gentle compressor at import. If you're building a Shortcuts automation, do the normalization in the audio file itself — Shortcuts can't adjust playback gain at runtime. Skip this step once and you'll learn the hard way the first time you connect at 7 AM with your wife in the passenger seat.
If you want sounds without picking
Our sound packs ship curated CarPlay startup and disconnect sounds across eight packs (Tesla-style, luxury chimes, retro arcade, minimal pings, engine starts, voice cues, sci-fi, and a proper silence preset for people who never wanted a sound). Plus the custom .m4a import, with in-app trim. Annual subscription, free to try.
FAQ
Can you change the CarPlay startup sound?
Yes, two ways in iOS 26: an app like Car Play Connect with built-in chimes (set once in the app), or a Shortcuts automation “When CarPlay connects → Play Sound” with any .m4a file under 10 seconds. The iPhone Settings app has no built-in toggle for this.
How do I change the CarPlay sound for free?
Use the Shortcuts route: create an automation that triggers when CarPlay connects and plays your audio file. It works, but adds a 1–2 second delay when the phone is locked — the dedicated-app route plays instantly.
What is the default CarPlay connection sound?
Two beeps a half-second apart, the second slightly lower, with an 880 Hz (A5) fundamental on the first tone. It has been unchanged since CarPlay launched in 2014.
Can I use my own audio file as the CarPlay startup sound?
Yes. Import any .m4a under 10 seconds — either as the sound in your Shortcuts automation, or via the custom import (with in-app trim) alongside the built-in presets in Car Play Connect.

