Add an audio version to your Webflow articles
Webflow has no plugin marketplace, but you can still add audio without a developer: script embed, RSS feed or API. The three methods, step by step.
Webflow appeals to studios and marketing teams because it lets you build a clean site without writing code. The flip side is that it has no plugin directory like WordPress: when you want a server-side feature, you often have to find something that plugs in through the front end, with no back office to modify. Adding an audio version of your articles is one of those cases. The good news is that on Webflow, audio drops in without a plugin and without a developer. Here are the three ways to do it, from fastest to most automated.
The player: an embed in your CMS template
Webflow serves articles through its CMS Collection. Each article is rendered by a template, and that template is where everything happens. Add a single Embed block there and the audio player shows up on every one of your posts at once.
The block holds one line:
``
<script src="https://wedispatch.fr/player.js"
data-article="ARTICLE_ID" defer></script>
Drop this embed exactly where you want the player to appear (right under the title, before the first paragraph, wherever suits you). Because it lives in the template rather than inside each article, you paste it only once. Every future post inherits the player automatically.
Linking the player to the right article
You still need to tell the player which audio matches which article. There are two approaches, depending on how comfortable you are in Webflow.
The first lets detection run off the page URL. You give WeDispatch the address of your article, the text is pulled from the published page, and the audio is matched. No field to create in your Collection.
The second, more robust, adds a custom field to your CMS Collection (a text field named audio, for example) that you bind to the embed's data-article attribute. That gives you a stable identifier even if the article URL changes one day. This method takes five minutes to set up, but it saves you from surprises during a URL redesign.
Three ways to generate the audio
Showing the player is not enough: you still have to produce the file. On Webflow, three routes are open to you.
The RSS feed is the simplest. Webflow natively exposes a feed for each Collection (the URL usually ends in /feed). You send us that address, new articles are detected as they publish, the text is extracted and the audio generated without any action on your side. It is the ideal option for a team that wants to publish as usual and find the player online automatically.
The sitemap approach works on the same principle if you would rather point at your site map than a feed. Useful when not all your pages go through a Collection.
Finally, if you need control (generating audio at a specific moment, choosing the voice, handling corrections), the API stays open. A Webflow site can trigger a call through a webhook or an automation tool like Make or Zapier at publish time. It is more work up front, but it hands you the whole chain.
Read-along and accessibility
Whichever mode you pick, you can turn on read-along: the text appears and highlights word by word as the audio plays. On a showcase site or a brand blog, that detail matters a great deal for dyslexic or visually impaired readers, and it fits a serious accessibility effort rather than a cosmetic one. Synced subtitles are configured from your dashboard, without touching any Webflow code.
When an article changes
On Webflow, republishing an article after an edit is common. If you go through the RSS feed, detection spots the update and flags the audio as "to regenerate": you relaunch generation once the text is stable, and successive corrections are never billed again. If you go through the API, just send the same external identifier with the corrected text. In both cases, the audio already online keeps being served until you relaunch, so no page is ever left without a player.
Where to start
For a Webflow site, the fastest route is the RSS feed combined with the embed in the template: fifteen minutes to set up, no code, and every new article ships with its audio version. If you want fine control or stable identifiers, add a CMS field and the API. The technical details are in the documentation, and the plans by article volume on the pricing page. The easiest way to decide is still to see the player running on your own pages: try it on one article and listen to the result before equipping the whole site.
Give your articles a voice with WeDispatch
This blog is itself voiced by WeDispatch. Curious how it sounds on your content?
Book a demo