Which audio player template for your blog: a decision, not a gallery
WeDispatch offers more than a dozen audio player templates. The right question is not which looks best, but which fits your page and what your article actually holds. Each model, what it requires, and how it falls back to the bar when the data is missing.
When you add listening to a blog, you quickly land on a grid of thumbnails: bar, card, banner, waveform, guided reading. The temptation is to pick at a glance, whichever looks best on the demo layout. That is the reliable way to find yourself, three weeks later, with a player that renders differently than expected on half your articles. Choosing a template is not a matter of taste, it is a decision, and you make it by looking at two things: your page, and what your article actually contains.
The catalogue now holds more than a dozen models, and that is not an argument. Adding one helps nothing if you do not know which to pick. So what follows is not a guided tour: it is the only useful thing, namely what each one asks for and who it suits.
The distinction that decides everything: what the template requires
A template is, first, the box around the player. But some models do more than draw a box: they display a piece of data the article must have. And if that data is missing, the model cannot serve.
The rule is simple and holds for all of them: a player that cannot serve falls back to the compact bar, it never fails. For the visitor it is silent: they see a bar that works, not a broken player. For the editor it is visible in the dashboard, where each template is shown alongside what it needs. In other words, you break nothing by choosing an over-demanding model; you simply get the bar instead, on the articles that lack the data.
Three pieces of data condition the most interesting models: word-level timing (the moment the voice starts and ends each word), a summary, and a split into chapters.
The models that require nothing
These work on any article, because they ask only for audio.
The compact bar is the safe choice when in doubt: thin, it slips under the headline without disturbing anything, on any layout. It is also what applies when nothing is set, and what everything falls back to. The card puts audio forward in a box that stands on its own, with the title: for a standalone piece. The minimal blends into the flow of text on a page that is already busy. The wide banner takes the full width when listening is the offer, best avoided in a narrow column. The compact is the slimmest version, for a sidebar or a tight space. The magazine reads like a standfirst, for an editorial layout. The single bar holds on one sixty-pixel line and never wraps: it is the most discreet, the one an integrator accepts without negotiating space above the article. The waveform replaces the progress bar with a wave shape, useful on long formats because it shows at a glance how much is left.
None of these eight can fall back for lack of data: they hold everywhere. The choice between them is purely about space and the tone of the page.
The models that require a piece of data
This is where the decision really happens.
Guided reading requires word-level timing: each word lights up as the voice reads it, and clicking a word jumps there. It is the model for accessibility (dyslexia, language learning) and for long reads followed on screen. Without timing, it falls back to the bar. We laid out that data and what it enables in guided reading, word by word. The unfolded text rests on the same data: the synced text opens inside the player card, and the rest of the settings sit behind a single button. It is the most versatile default, as soon as the article has its timing. The shareable quote requires it too: the listener selects a passage and gets a link that starts exactly there.
Two others depend on something else. Summary first needs a summary to exist: the thirty-second gist up front, the full article one button away. The episode, in podcast format, needs a split into chapters: cover art, clickable outline, fifteen-second skip, resume where you left off.
The floating bar, for its part, requires no article data, but it has a condition of another kind: it follows the page scroll, and that detachment is done by the host page, not by the player. We explain that mechanism and its behaviour on mobile in a dedicated article.
How to decide, in practice
Start from your article before you start from the drawing. Do your articles carry word-level timing? Then guided reading, unfolded text and the shareable quote are open to you, and that is where the product shows what it can do. Do you have summaries, chapters? Summary first and the episode become relevant. Otherwise, stay with the models that require nothing, and choose by the page: dense, editorial, or audio-first.
The setting itself lives in your dashboard, per account or per site, and it applies to both the on-screen player and the recording. To see how the player then slots into a site without touching the theme, our WordPress page describes the install path end to end, and the audio player page shows the models in context.
The right template is not the most spectacular one. It is the one that fits your page and that your articles can actually serve. Everything else falls back to the bar, and the bar, at least, works everywhere.
Give your articles a voice with WeDispatch
This blog is itself voiced by WeDispatch. Curious how it sounds on your content?
Book a demo