# How to Set a Custom Notification Sound for One Contact on Android
Imagine being able to tell who is texting you without even glancing at your phone. A specific chime for your partner, a different ding for your boss, a sharp tone for your kid's school. Android lets you assign a custom notification sound to individual conversations, so the sound itself becomes the caller ID for your texts.
The feature is powered by Android's notification channels: most modern messaging apps let you override the sound for one conversation at a time. This guide shows the exact steps for Google Messages and Samsung Messages, how to add your own sound files, troubleshooting when the sound does not stick, and the limits you should know before you start.
What Android Can and Cannot Do
First, a clear picture of the mechanics, so the settings make sense:
- Android assigns notification sounds per conversation thread, not per contact card. The custom sound lives on that chat thread inside the messaging app.
- You can give the same person one custom sound in Google Messages and the default sound in another app, because each app keeps its own settings.
- Google's official help confirms you can change notifications for individual conversations, including marking a conversation Important so it always alerts you. See Google's guide to conversation notifications.
- Group chats get their own override too, independent of one-to-one chats with the same people.
What you cannot do: there is no single Android setting that makes one contact's sound follow them across every app. If you want the same custom tone in Google Messages, WhatsApp, and Telegram, you set it once in each app.
Set a Custom Sound for One Conversation in Google Messages
Google Messages is the default texting app on most Android phones, and its per-conversation sound override takes under a minute.
- Open Google Messages and tap the conversation you want to customize.
- Tap the three-dot menu in the top-right corner, then tap Details.
- Tap Notifications.
- If you see a Custom notifications toggle, turn it on. This unlocks the per-conversation options.
- Tap Sound.
- Pick a sound from the list. Tap each name to preview it, then confirm with Save or OK.
That conversation now plays your chosen sound. Every other chat keeps the default. If you want to set the default itself for all chats, go to your profile icon, then Messages settings, then Notifications, then Incoming messages, then Sound.
A useful companion setting lives in the same Details panel: Priority. Marking a conversation as Priority puts its notifications at the top of the shade and lets it break through Do Not Disturb. Pair a custom sound with Priority for the two or three people you never want to miss.
Do the Same in Samsung Messages
Samsung's One UI keeps the same idea but with its own layout.
- Open the conversation, tap the three-dot menu, and open the conversation's notification settings.
- Enable custom notifications for that thread if the toggle is present.
- Choose the Sound option and pick your tone.
If you use Google Messages on a Samsung phone (very common on newer models), use the Google Messages steps above; the system notification categories for Google Messages must have Manage notification categories for each app enabled under Settings, Notifications, Advanced settings. This is a known quirk on One UI where the per-app sound options stay hidden until that toggle is on.
Add Your Own Sound File as the Alert
Built-in tones are short and safe, but many people want something personal: a snippet of a song, a recorded phrase, a funny effect. You can add your own audio file to the phone's notification sound picker.
- Save your audio as an MP3, OGG, or M4A file. Short clips work best; anything over 5 to 10 seconds feels too long for a text alert. Keep the volume balanced so it is not quieter than the built-in tones.
- Copy the file into the Notifications folder in your phone's internal storage. If there is no Notifications folder, create one at the top level of internal storage.
- Restart the messaging app, then repeat the per-conversation steps above. Your file now appears in the sound list.
If your file does not appear, open the Files app and confirm the folder name is spelled exactly Notifications, and that the file is directly inside it rather than in a subfolder. Very long file names or unusual characters can also hide a file from the picker.
Troubleshooting: When the Custom Sound Does Not Stick
Three problems account for nearly every report of a custom contact sound failing.
- The thread was deleted. The custom sound is attached to the conversation thread, not the contact. Deleting the whole thread wipes the override, and the next message from that person uses the default again. Archive instead of deleting, or use automatic message cleanup so the thread survives.
- Do Not Disturb is silencing everything. Check that the conversation is marked Priority, or add the contact to your DND exceptions, otherwise your custom sound never gets a chance to play.
- The sound picker shows no custom files. The app needs storage/media access permission to see your files. Long-press the Messages app icon, open App info, then Permissions, and grant media access. On some phones you also need to clear the Media Storage cache (Settings, Apps, show system apps, Media Storage, Storage, clear cache) for new files to register.
One more common surprise: when the conversation is open on screen, Google Messages plays only a subtle blip instead of your custom sound. That is intentional behavior across most messaging apps: the phone assumes you are already looking at the chat, so it does not fire the full notification.
Limitations to Know
- The override is per app. Custom sound in Google Messages does not carry over to WhatsApp or Telegram; each app needs its own setup.
- Some third-party SMS apps use their own internal settings and ignore the system picker. If the sound option never appears, check inside the app's own settings menu.
- Battery saver and aggressive background restrictions can delay notifications, which also delays your custom sound. If alerts arrive late, exempt the messaging app from battery optimization.
- On older Android versions (before Android 8), per-conversation notification channels do not exist, so only the app-wide default sound can be changed.
Frequently Asked Questions
Will the custom sound work if I set it in Google Messages but use RCS chat features?
Yes. The per-conversation sound applies to both SMS and RCS messages in the same thread, because the override is tied to the conversation, not the message protocol.
Can I set a different sound for a group chat?
Yes. Open the group conversation and follow the same steps: three-dot menu, Details, Notifications, Sound. Group overrides are independent of your one-to-one chat overrides.
Why does my custom sound reset after a phone update?
Major system updates occasionally rebuild notification channels, which can drop per-conversation overrides. Re-assigning the sound takes a minute, and the audio file itself stays on the phone.
Does a custom sound use more battery?
No. The sound file is local and tiny; playing it costs no more energy than playing a built-in tone.
Can I use different custom sounds for calls and texts from the same person?
Yes. The text sound you set here only affects messages. To set a custom ringtone for that person's calls, edit the contact itself and set its ringtone, or see our guide on setting a ringtone for one contact on Android.
Related Guides
If you are customizing sounds across your phone, these guides fill in the rest of the picture: Android default notification sound explained for the difference between notification and call sounds, different notification sounds per app on Android for app-level overrides, and Google's official sound and vibration settings for the system-level controls.
Assign one custom sound to your most important conversation today. In a week you will wonder how you ever dug your phone out of your pocket for every buzz.