← Blog · 15 November 2026 · Lire en français

White-label audio player: where your logo goes, and where our name still shows

Putting your own logo on the audio player under your articles is usually the first thing a publisher asks for. What white-labelling actually changes, who gets it, which files work, and the three places our name remains, stated plainly.

Ask a publisher what bothers them about an embedded audio player and you rarely hear about the sound. You hear about the corner of the player where somebody else's logo sits. It is a small thing, a few pixels under every article, and it quietly tells each reader that part of the page belongs to a vendor. For a newsroom that has spent years building a masthead, that is enough to delay a rollout.

So the request is reasonable, and on paid accounts the answer is yes. But "white label" is one of those phrases that tends to promise a complete disappearing act. This article describes what it does in our player, as the code implements it, and is just as specific about what it does not do.

One corner, three possible states

The brand slot in the player can show one of three things, depending on the account.

  • Free trial: a readable "Audio by WeDispatch" badge, clickable, linking to our site. It is the price of the free tier and it cannot be switched off. A free account keeps the badge even if it has uploaded a logo.
  • Paid account, no logo uploaded: our small logo on its own, no text, linking to our site.
  • Paid account with a logo: your logo and nothing else. It is not a link, because it stands for the publisher rather than advertising anyone, and it is marked as decorative (empty alt text) so a screen reader does not announce it on every article.

One exception worth knowing about: partner plans, granted as part of a partnership rather than bought, do not include white-labelling. The badge stays there. That is the line between a partnership and a discount.

Upload rules, and why they are tight

The logo is uploaded from the Appearance screen of the dashboard, in the "Your logo in the player" card. Four formats are accepted (PNG, JPEG, WebP and SVG) with a 512 KB ceiling. The logo renders 22 pixels tall (18 in the minimal template) and at most 120 pixels wide, scaled without distortion. A heavier file would only slow the page down; it would not look any sharper at that size.

Those dimensions lead to two practical tips. Use the horizontal version of your mark, or the symbol alone: a square logo with a tagline underneath turns into a smudge at 22 pixels. And if you have an SVG, use it. It stays crisp on every screen and is almost always lighter than the equivalent PNG.

Every upload is stored under a fresh file name, and the previous file is deleted. In practice that means a replaced logo shows up straight away instead of waiting for a cache somewhere to expire. Only the account owner and administrators can change or remove it. A team member who publishes articles cannot alter the brand shown under every article on the account, which is the point of having roles in the first place.

Several sites, several brands

A media group or an agency often runs more than one title from a single account, and the titles do not share a masthead. The logo can therefore also be set per site, in each site's settings. The rule is simple: a site with its own logo shows it, a site without one inherits the account logo. How multi-site accounts work in general is covered in our guide to managing several sites from one account.

The logo is only one part of looking like yourself. The player's accent colour follows your site, and the article on automatic player colours explains why a brand that lives only inside a logo image is invisible to that detection. The typeface can be one of four system font families, so no font is fetched from a third-party server. For anything beyond that, a custom stylesheet of up to 4,000 characters is available. It is sanitised on save and again on display: @import rules and anything resembling executable code are stripped out.

What still carries our name

An honest white label tells you where it stops. There are three places.

The player's accessible name. For screen readers, the player is a group labelled "WeDispatch audio player, listen to the article". A blind visitor therefore hears our name on reaching the player, even when your logo is the only thing displayed. That is a real limitation of the current white label, and we would rather state it here than have you find it during an accessibility audit.

Pages we host. The listen link you can put in a newsletter and the page that gathers all of your audio are served from our domain. Your logo appears there (with your publication's name as alt text this time), but it is the account logo, not a per-site one. Both pages carry a noindex instruction, so they never compete with your own pages in search results.

The synthetic voice notice. By default, a line under the player says the voice is synthetic. It does not mention us, but white-labelling does not remove it either: it is a separate setting, on by default, that a publisher can turn off deliberately. Our reasons for showing it by default are set out in the article on disclosing a synthetic voice.

Seeing it before deciding

If your site runs on WordPress, the quickest way to judge the result is on a real page rather than a mock-up. The WordPress plugin downloads without an account and places the player without editing your theme. You will see the free-trial badge at first, which is expected, and you will know exactly what space your logo will take.

White-labelling does not make the audio any better. It simply stops your article page from talking about someone other than you. That is a modest goal, and it is precisely what it should do.

Give your articles a voice with WeDispatch

This blog is itself voiced by WeDispatch. Curious how it sounds on your content?

Book a demo

Read next