Notification Sounds

Adding custom sounds to mobile notifications.

Custom sounds are a way to provide a more unique, branded experience for your app. You may add a custom sound with every notification you send, or you may add sounds to just certain types of notifications. For instance, a game like "Jewel Breaker" may wish to have a jewel-like sound always played when receiving notifications. Meanwhile, a social network may wish to only play sounds when the user receives a message from another user to differentiate those notifications from more generic system notifications.

For mobile apps only. Not supported on web push.

Step 1. Create Sound Files

Be sure to create sound files according to the following rules. If the device cannot find the file in question, or if the file is not in a supported format, it will fall back to the default system notification sound.


Sound Filename Recommendation

Keep sound filenames lowercase since some platforms ignore upper case letters for sound files. Instead of AwesomeSound.wav use awesomesound.wav or awesome_sound.wav.

iOS.wav .aiff .cafApple is picky about file formats. Sounds must be encoded as Linear PCM, MA4 (IMA/ADPCM), µLaw, or aLaw. Must be less than 30 seconds.
Android.wav .mp3 .ogg
Amazon.wav .mp3 .ogg
Windows.wav .mp3 .wmaMust be less than 10 seconds

Step 2. Add Sound Files to App

To adds sounds to notifications, you must include the sound files as resources within your app. External URLs are not supported.


Add sound files to the appropriate location in your Xcode project depending on your SDK.

iOS NativeAdd files to the Xcode project root. Make sure Add to targets is selected when adding files so that they are automatically add to the bundle resources.
Cordova, IonicAdd files to Resources directory within the Xcode project in <project-root>/platforms/ios/project-name.xcodeproj.
UnityAdd sounds anywhere in your Unity project, build your project, and then move those sounds to the Xcode project root.

Android and Amazon

Add sound files to the appropriate folder in your project depending on your SDK. If the folder does not exist, create it.

Android & Amazon Nativeres/raw
React Native<project-root>/android/app/src/main/res/raw

NOTE: Your sound and icon file names must be lowercase and can't contain anything else except underscores and numbers.
.NET MEUI<project-root>/Platforms/Android/Resources/raw/

Step 3. Send Notifications With or Without Sounds

Android & Amazon

Android 8+ introduced Notification Categories which must be setup to customize notification sounds. OneSignal will use the sound set in the Notification Channel for all versions of Android.

In Settings > Messaging > Android Notification Categories create the group and channel.

Set Importance to "Urgent" or "High" to play sound.
Set Sound to "Default" or "Custom" based on your needs. Do not add the file extension when referencing the sound resource. For instance, cat_meow_sound.

For no sound, set Importance to "Urgent" or "High" and Sound to "Off". Or you can set Importance to "Medium" or "Low" for no sound.

You can then set the category name in the Dashboard Push Messages or use the API android_channel_id property. The sound set in the category will work for all android versions.


Add the file extension when referencing the sound resource. For instance, explode_sound.wav.
Set in the Dashboard Push Messages or use the API ios_sound property.

For no sound, pass in nil to the Sound field.


Instead of sending via the dashboard, you can send notifications with sounds in the REST API by using the appropriate parameter and file extension depending on your platform (see more in Create notification REST API docs).

PlatformAPI ParameterDetails
iOSios_soundInclude File Extension.

ios_sound : expload_sound.wav

No sound, pass nil.
Androidandroid_channel_id - Use if you created channel in the OneSignal Dashboard Notification Categories.

existing_android_channel_id - Use if you created the channel elsewhere
Highly recommended to use Android Notification Categories
Amazonadm_soundDo Not Include File Extension.

adm_sound : exploade_sound


New sounds take a while to propagate to all users

If you've very recently added a sound resource to your app, you may want to wait a few days before sending notifications using the sound. This is because it can take many days or even weeks for the majority of your users to update their apps to the latest version which contain your new sound resource.

If a user has an older version of your app without the sound resource and receives a notification that references it, they will hear only the default system notification sound.


Can I set a default sound?

OneSignal does not support default sounds directly. However, a workaround is to create a Template that references the sound, and use that that template for every message you send.

Why is my notification not playing the custom sound file?

There are a few reasons why a sound may not play.

  • Sound file has an incorrect file extension
  • Sound file is not encoded in a supported format
  • Sound file is in the incorrect location
  • Sound file is too long

Currently OneSignal does not log the resource incorrect issues, we're working on adding this to your logs.

iOS - Read more in Apple's documentation for tips on how to encode files and test them.

Android - Make sure that it is getting built into your APK by extracting it and making sure it is located in res/raw/.

If shrinking resources is enabled, you can protect sound files from being removed by creating keep.xml in res/raw/ with following code

<resources xmlns:tools=""

Why is my notification playing the default sound file?

Please make sure that you followed the setup instructions carefully and the sound file is in the correct location for the SDK.

Why is the wrong sound playing?

On Android, notifications will get grouped together after a certain amount are received by the device without opening them. Grouped notifications play a default sound. You can set the sound with the GROUPKEY for all your notifications.

What’s Next

Learn about setting up more features, or start using the OneSignal Dashboard