Adding audio to a TYPO3 site: the plain route, not an extension
TYPO3 runs a lot of university, government and large-publisher sites. Here is how to add an audio version of your articles without writing an extension or weighing down your upgrades.
TYPO3 is rarely the CMS behind a personal blog. It is the one universities, public administrations, large institutions and serious publishers reach for when they manage hundreds of pages, fine-grained access rights and long update cycles. That sturdiness comes at a cost: in TYPO3, adding a feature often means an extension, which means code to maintain, to audit, and to carry forward through major version upgrades that are never trivial. Voicing your articles should not fall into that category. Here are the three ways to add an audio version to a TYPO3 site, from the lightest to the most integrated, and why we point you at the first one.
Option 1: the plain HTML content element, no extension
The fastest route uses no third-party extension at all. TYPO3 ships with a "Plain HTML" content element, and you simply paste our embed snippet into it. You add it to your article layout, or into a content footer container, and the player detects the page text and offers playback. Nothing to install from the TER, no extra dependency to update, no additional security review to schedule.
This is the option we recommend to start. It lets you test audio on your real site in an afternoon, without pulling in your integrator or freezing a deployment window. Its limit comes down to how you manage your templates: if your site rests on a tightly governed set of TypoScript and Fluid, have the person who owns those templates place the element, so it appears in the right spot on the right page type and nowhere else.
Option 2: the RSS feed, to automate without touching templates
TYPO3 can produce feeds, whether through the most common news extension or a dedicated view. By pointing our service at your RSS feed, every newly published article is picked up and its audio version prepared automatically, with no editor having to click. Your TYPO3 editorial chain stays intact: the newsroom publishes as usual, and the audio follows.
There is one thing to check, and it is always the same: your feed has to expose the full article body, not a summary. Many TYPO3 setups truncate the feed by default to keep the page light. If the feed is cut, the audio will be too. This is also the approach that feeds an automatic podcast from your regular output, with no separate project.
Option 3: the API, when a precise need justifies it
If your team wants to decide exactly when and how audio is generated, the API is the right path. You trigger narration from a TYPO3 hook, for example when a record is published, and you fetch the file reference to display it wherever you want in your Fluid template. It is more work up front, but it opens the edge cases: voicing only certain sections, regenerating audio when an article is corrected, or storing the reference in a field specific to your data model.
Save this route for sites that genuinely need it. Most TYPO3 installs are better served by the first two options, which are plainer to maintain over time.
What the integration does not touch
The point that reassures a TYPO3 team used to being wary of grafts: in all three cases, your installation undergoes no heavy transformation. The HTML element writes nothing into your schema, the feed does not change your publishing chain, and the API forces no dependency into your composer.json. You can reverse course by removing a block or switching off the feed, with no reverse migration. It is the same logic described for a headless CMS or a static site: the audio sits next to the content, it does not stand in for it.
Accessibility, often the real reason
Many TYPO3 sites are in the public sector and therefore covered by web accessibility law. One point deserves to be clear: the audio version is added to your page, it does not replace your HTML. Your text stays fully present, readable by screen readers, and the synced text that accompanies playback is that same content. You strengthen accessibility without degrading what exists, which is exactly what an audit expects. Audio is not an accessible alternative to text, it is a listening comfort added to a page that is already compliant.
In short
Start with the HTML element to test, move to the RSS feed to automate, and only reach for the API if a precise need calls for it. In all three cases your TYPO3 install stays in charge of its own house, and you keep the option to step back at any time.
Add audio to your TYPO3 site with WeDispatch
Whether you start from the HTML block, the RSS feed or the API, switching it on is free and reversible. Give it a try on a few articles before rolling it out.
Give your articles a voice with WeDispatch
This blog is itself voiced by WeDispatch. Curious how it sounds on your content?
Book a demo