Design & Branding Guidelines

Welcome to our hub for partner guidelines and assets. We want to make it easy for you to integrate Spotify in your platform while respecting our brand and legal/licensing restrictions. These guidelines are meant to help any external developer integrating Spotify into their product while ensuring all Spotify users receive the same delightful user experience - no matter which platform they listen on.

By using these resources, you accept our Developer Terms of Service. Usage of these resources may also be covered by the Spotify End User Agreement and our Privacy Policy.

---

Content available through Spotify is owned by many different rights holders. If you use any Spotify metadata (including artist, album and track names, album artwork, and audio playback) it must always be accompanied by the Spotify brand.

To comply with our licensing agreements, you must always attribute content from Spotify with the logo. In partner integrations, you should always use our full logo (icon + wordmark). We do allow using only our icon if it's featured as an app icon on the app screen of a device.

• The full logo is the combination of a wordmark with our icon.
• Our icon is a shorter version of our logo. Only use it if you do not have enough room for the full logo.

Full logo and icon use must comply with our Logo & Color Guidelines.

---

If you're using artwork and/or metadata provided by Spotify.

• You may only use the artwork provided by Spotify.
• Artwork must be kept in its original form. Don't animate or distort it in any way. This includes applying overlays and blurring.
• Artwork corners must be rounded to create optical blending with nearby UI elements. Small & medium devices should use a 2px corner radius, whereas large devices should use a 4px corner radius.
• If screen real estate is limited, it's OK to not include any album artwork.

• Track, artist, playlist, and album titles must always be presented with the metadata provided by Spotify.
• The metadata must always be legible.
• You may truncate metadata if space is limited. The user should always be able to view the entire metadata.
• Don't manipulate any content or metadata.

For podcasts, two sets of metadata need to be supported:

• Title of episode
• Podcast name

We recommend using two lines in your layout for the title of the episode, since podcast episodes often have longer titles than music. The third line is then used for the podcast name.

For audiobooks, two sets of metadata need to be supported and one is suggested.

• Title of book
• Name of Author
• Chapter if sharing

Your layout should be able to accommodate these character counts:

• Playlist/album name: 25 characters
• Artist name: 18 characters
• Track name: 23 characters

---

If your app links to a user's Spotify account and there's a dedicated space to display Spotify content. Platforms that aggregate content from multiple audio providers must give Spotify fair treatment - anything made available to all other partners must be available to Spotify.

• Spotify will provide rows - or shelves - of recommended content.
• Spotify provides metadata and decides what metadata should be shown to the user, such as headlines and naming of unique contexts and groups of contexts, for all relevant surfaces.
• Spotify should determine and populate your content categories. We've optimised our APIs to cover several use cases and serve the most relevant content to each user.

• Don't manipulate any content or metadata.
• Spotify content should never be seated next to content from similar services.
• Dedicate the full row (shelf) in the view to Spotify content.
• Never show more than 20 items in a content set. At the end of each content set, a link to the Spotify app should allow listeners to keep exploring the category.
• Use Spotify's logo or icon to attribute content.

---

On a platform where Spotify already exists. If you have built an integration on a platform where the Spotify client exists (mobile and desktop integrations), always link to the Spotify app. The Spotify app is the default playback mechanism. For full access to Spotify functionality, users should be directed to the Spotify application installed on the partner platform. If the app is not installed, the user should be directed to the app store so that they can install Spotify.

If you use any Spotify metadata (including artist, album and track names, album artwork and audio playback) it must always link back to the Spotify Service.

• If the Spotify app is not installed then the link should say, GET SPOTIFY FREE
• If the Spotify app is installed then use any of the following text strings: OPEN SPOTIFY, PLAY ON SPOTIFY or LISTEN ON SPOTIFY

The link to Spotify must follow Spotify's attribution requirements and be accessible in your companion app.

---

When you're showing any playing views in your app.

• Follow Spotify's attribution requirements, you must always attribute content from Spotify with either the Spotify logo or icon.
• Follow the artwork and metadata requirements.
• Always link to the Spotify app (when the Spotify client is available on platform).

It is recommended that no play controls other than play/pause are provided in your app.

Disabling and enabling play controls in response to restricted actions for Spotify Free may result in a confusing experience for the user. For example, the user may not understand why the skip back option has been disabled. Rather than explaining these restrictions to the user or creating a frustrating UX, we recommended you don't provide play controls.

If you choose to show play controls in your app, the following requirements need to be followed:

• Use the restrictions returned in PlaybackRestrictions to correctly set the playback state in the companion app and to respond to the user when they try to perform a restricted action.
• Play controls must either have a disabled state to indicate that they are restricted or they should not be displayed at all.
• Make clear that the track progress bar is for information only - there should be no indication that the user can seek.

When the user tries to perform a restricted action you may display this messaging.

Spotify Premium lets you play any track, podcast episode or audiobook, ad-free and with better audio quality. Go to spotify.com/premium to try it for free.

• Podcasts need to have the option to seek 15 seconds forward or backwards.
• Audiobook samples also need to have the option to seek 15 seconds forward or backwards.
• You can parse the track URI in order to differentiate between podcast episodes and regular tracks.

In all playback views where content from Spotify is playing (fullscreen views, widgets, bars, skipped song notifications) make sure to follow these guidelines:

The Like feature should signal back to Spotify and the liked content must not be saved by the partner. When the user taps the + icon, they are liking a song or episode. The icon should change to its active state and show a message saying "Added to Liked Songs" or "New Episodes". If the user taps the + icon again to unlike the song, show a message saying "Removed from Liked Songs" or "Removed from New Episodes". The like action is always represented with the + icon and can be downloaded here:

---

In Spotify Free, for on-demand playback and shuffle play.

For Spotify Free, you have to support two types of layouts for tracklists when showing a playlist/album entity:

For on-demand playback, the user will be able to see and play all tracks in the playlist/album.

For shuffle play the user will only be able to see a content summary of the playlist/album and then start shuffle playback. The user can't pick a particular song to play, it will start playback in shuffle.

Using the Web API, your app can determine whether or not a track or a podcast episode is marked as containing explicit content. Consider using this information in your app to help users discover the content that is appropriate for them.

Apps that serve users in South Korea should follow local regulations governing explicit content. When displaying a tracklist or a piece of content to a user in South Korea, your app must display an explicit content badge next to the title of any explicit track or podcast episode. See the Web API reference documentation for more information about the explicit field.

	Sample explicit content badge for a white background
	Sample explicit content badge for a dark background

---

We are very proud of our logo. Follow these guidelines to ensure it always looks its best.

Our full logo is the combination of our logo icon and the wordmark.

Our icon is a shorter version of our logo. Use the icon on its own only if you do not have enough room for the full logo or in cases when the Spotify brand has already been established. While the icon can exist without the wordmark, the wordmark should never exist without the icon.

The Spotify green logo, pictured top left, is our primary logo colorway, and it should only be used with black, white, and non-duotoned photography.

The Spotify green logo should only be used on a black or white background, for any other background you should use a monochrome logo.

The black logo should be used on light colored backgrounds. The white logo should be used on dark colored backgrounds.

Our logo should always be legible and impactful. Always apply the logo and the icon's exclusion zone to isolate the logo from competing visual elements such as a busy area of an image, low contrast areas where legibility is compromised, or on top of text or supporting graphics. The exclusion zone is equal to half the height of the icon (marked as × in the diagram).

Establishing a minimum size ensures that the impact and legibility of the logo aren't compromised.

It's important that the appearance of the logo remains consistent. The logo should not be misinterpreted, modified, or added to. Its orientation, color, and composition should remain as indicated in this document — there are no exceptions.

---

While embracing a much more colorful language in our brand communications, Spotify Green is our resting color, used whenever Spotify's voice needs to be recognizable.

---

If you are registering your application with us (on the Dashboard page) you will need to enter the name of your app. This name will be used in communications to your app's users when you seek authorization to access their data. We have a few pointers to consider when naming your app:

The app name should not include 'Spotify' or be similar to 'Spotify' in sound or spelling. It shouldn't imply endorsement by Spotify, but suggesting to users that it is 'for Spotify' is acceptable.

Your logo should not include, or look similar to the Spotify logo or any of its brand elements (e.g. Spotify Green, the circle, and the waves). Don't incorporate Spotify's trademarks, in whole or in part, in the name of your company, product, application, service, or website.

Don't use the Spotify brand together with any other brand or in any co-branded communications. Pairing of brands is not permitted under our Developer Terms.

---

We recommend you to use the default sans-serif font for the platform you are working on. Try commonly available defaults in this order:

• Default sans-serif for the platform
• Helvetica Neue
• Helvetica
• Arial

---

If you are having trouble with anything in this guide, you are missing brand elements from the brand package, or you are unsure if your communication best represents the Spotify brand, please contact the Spotify brand approval team at brandapproval@spotify.com.

For additional programming resources, check out Stack Overflow (tag: Spotify).