- Capture at the right format
- Export two files, not one
- Hosting that does not slow the page
- The embed block, done properly
- Recording it in the first place
- Checking before publish
- Frequently Asked Questions
- Should I use a plugin for audio?
- What bitrate for podcasts?
- Can I host audio on the same server?
- Do transcripts really matter?
WordPress makes embedding audio trivial and hosting it expensive if you get the format wrong. A five-minute recording can become a 40 MB file that slows every page it appears on. The fix is a short, fixed workflow from capture to embed.
Capture at the right format
Record at 48 kHz mono, 16-bit or 24-bit. Mono halves the file size and voice carries no useful stereo information. Recording in stereo and downmixing later costs bandwidth and gains nothing.
- Mono, not stereo
- 48 kHz capture, resample once at export
- WAV for the master, never MP3
Export two files, not one
Produce a master WAV for archival and an MP3 at 96 to 128 kbps mono for the post. Speech at 96 kbps mono is transparent on every device that matters, and the file is roughly a tenth of the WAV.
| Use | Format | Typical size (5 min) |
|---|---|---|
| Master | WAV 48 kHz mono | 28 MB |
| Post embed | MP3 96 kbps mono | 3.6 MB |
| Podcast feed | MP3 128 kbps mono | 4.8 MB |
Hosting that does not slow the page
Uploading to the WordPress media library is convenient and often the wrong choice: the file is served from the same server as the page, and large media transfers compete with HTML delivery. Use a dedicated audio host and embed the player, or at minimum offload media to object storage.
- Dedicated audio host for anything over 5 MB
- Media offload plugin if you must self-host
- Never autoplay: it costs bandwidth and annoys readers
The embed block, done properly
Use the core Audio block with a transcript below it. Search engines cannot listen, and a transcript is the only way the content is indexable. It also makes the post accessible, which is a ranking factor in its own right.
- Audio block, not an iframe from a third party
- Transcript in a collapsible block below
- Descriptive title attribute on the player
Recording it in the first place
A phone on a stand 15 cm from the mouth, connected over USB, is enough for interview clips and narration. The https://womic.io/wo-mic-apk/ covers the Android-side settings that keep the stream alive when the screen sleeps, which is the failure that ruins most phone recordings.
| Setting | Value | Why |
|---|---|---|
| Battery optimisation | Off for the app | Prevents suspension mid-recording |
| Screen timeout | Long | Radio stays out of power save |
| Do not disturb | On | Stops notifications bleeding into the take |
Checking before publish
Play the embedded file on a phone over mobile data, not on the office Wi-Fi. If it buffers, the bitrate or the host is wrong. Then open the page in a private window and confirm the transcript is visible without JavaScript.
Frequently Asked Questions
Should I use a plugin for audio?
The core Audio block is enough for most sites. Plugins add player styling and analytics but also weight.
What bitrate for podcasts?
128 kbps mono for speech. Above that the difference is inaudible on typical playback equipment.
Can I host audio on the same server?
For small files, yes. Above roughly 5 MB per episode, offload it or the page speed will suffer.
Do transcripts really matter?
Yes. They make the content indexable and accessible, and they are the cheapest SEO win available for audio.