Elementor Integration
Dynamic rendering patterns and article audio placement.
Page Builder Integrations
Use WPVoicer audio output in real builder workflows.
WPVoicer is built to work with common WordPress builder stacks so teams can render dynamic post audio, including optional intro/outro text in the generated MP3, without custom pipeline work.
Integrations
Dedicated implementation pages.
Each page covers the specific implementation context and expected publishing behavior for that builder.
Implementation map
All integrations start from the same WPVoicer output: the generated MP3 attached to the current WordPress post. If intro/outro text is enabled in the plugin, it is already part of that audio file; the builder only needs to read the right dynamic value.
Elementor ProUse WPVoicer Audio URL in dynamic URL fields, or WPVoicer Audio ID where an attachment ID is required.
BricksUse {wpvoicer_audio_url} for the MP3 URL, or {wpvoicer_audio_id} for the Media Library attachment ID.
BreakdanceSelect Dynamic Data -> WPVoicer -> Audio URL in URL-capable fields.
Universal fallbackUse [wpvoicer_audio] when a shortcode-based player is the cleaner option.
FAQ
Integration questions.
What the page builders receive from WPVoicer and how the output is used.
Do integrations call the WPVoicer API directly?
No. The builder reads the generated audio attached to the current WordPress post. WPVoicer handles generation, including optional intro/outro text, through the plugin workflow.
Which builders are currently documented?
The current implementation pages cover Elementor Pro, Bricks and Breakdance, with builder-specific fields and fallback shortcode usage.
Can the shortcode be used instead?
Yes. The universal fallback is [wpvoicer_audio] when a shortcode-based player is the cleaner implementation path.
Does each post get its own audio value?
Yes. The dynamic value resolves against the current WordPress post context, so a single template can render different audio files per article.