A QR code holds about a fifth of a second of sound
Worth getting out of the way first, because the phrase “audio QR code” implies something that is not happening.
The biggest QR code the standard allows (ISO/IEC 18004 version 40, error correction L) carries 2,953 bytes. At a normal 128 kbps MP3 that is 0.185 seconds of audio. Not a song, not a word, barely a click. Push the bitrate to 320 kbps and you are down to 0.074 seconds.
Here is the same point against files people actually want to share:
| What you want to share | Size | Versus the QR ceiling |
|---|---|---|
| 1-minute voice memo (64 kbps) | 0.5 MB | 163x too big |
| 3-minute song (128 kbps) | 2.7 MB | 975x too big |
| 3-minute WAV (44.1 kHz, 16-bit stereo) | 30.3 MB | 10,752x too big |
| 45-minute podcast episode (96 kbps) | 30.9 MB | 10,972x too big |
So an audio QR code stores a link. The phone scans it, opens the URL, and the audio plays from there. Every product in this category works this way. The question worth your attention is which URL goes in the square, and what happens in the two seconds after someone scans it.
Make an audio QR code
- Paste your audio link into the field above. Spotify, SoundCloud, Apple Music, a podcast episode, a Google Drive file, or a direct MP3 URL all work.
- Pick an error correction level. M is right for most things. Use H for anything that gets handled, laminated, or stuck to a wall.
- Download the PNG for slides and email, or the SVG for print.
The code is generated in your browser, so the link you type is never sent anywhere to build the image.
If your audio is not online yet, use the uploader in the second tab. It puts the file in ScreenApp and gives you a share link to encode.
MP3 to QR code, and every other format
A file on your desktop has no address, so there is nothing to encode. file:///Users/you/Music/demo.mp3 resolves only on your machine. This is true for MP3, WAV, M4A, AAC, FLAC, OGG, WMA, and AIFF alike. The container is irrelevant. Getting the file onto a public URL is the actual work, and encoding that URL takes a second.
Two format notes that matter in practice.
Do not put a WAV behind a QR code. A three-minute WAV is around 30 MB against 2.7 MB for the same thing as a 128 kbps MP3, roughly eleven times the download for audio most people will hear through a phone speaker. Convert to MP3 or M4A first. Anyone scanning on mobile data will thank you.
M4A from a voice recorder app is fine. iPhone Voice Memos exports M4A (AAC), which every current browser plays. This is the one Apple default that does not cause cross-platform grief, unlike HEVC video.
For the reverse job, pulling the audio out of a video before you share it, use extract audio from videos.
It will not play automatically, and that is not a bug
This is the single biggest gap between what people expect from an audio QR code and what browsers permit.
Chrome and Safari both block audio from starting on its own. Chrome gates autoplay behind prior user engagement with the domain, and Safari blocks sound-on autoplay outright by default. A scan is a first visit from a stranger’s phone to a domain it has never seen, which is exactly the case the policy exists to stop. So the person who scans your code lands on a page with a play button and has to tap it.
You cannot buy your way around this. No QR generator, paid or free, can override a browser autoplay policy, because the code is just a URL and the policy applies to the page.
What this means for your design: the landing page needs an obvious, large play control, and your printed material should say “scan and press play” rather than “scan to hear”. The extra four words prevent most of the “the code doesn’t work” complaints.
The iPhone silent switch catches people too. With the ring/silent switch flipped to silent, an iPhone can play nothing at all through Safari even after a tap. The visitor concludes your code is broken. If you are printing audio codes for a museum, a gallery, or anywhere visitors are likely to be on silent, put a line on the label: “turn off silent mode”.
Spotify, Apple Music, SoundCloud, and podcasts
Spotify. Two different things get called a code here, and mixing them up wastes a print run. Spotify Codes are the striped graphic Spotify generates in its own app, and they scan only through the search bar in the Spotify app. A camera pointed at one does nothing. A real QR code holding a Spotify URL opens in any phone camera, which is what you want on anything the general public will scan. Note that listeners without Premium hear ads, and in some regions shuffle restrictions apply, so a link is an invitation rather than a guaranteed playback of that exact track.
Apple Music. Long URLs, and non-subscribers get a preview rather than the full track. Fine for an audience you know subscribes, weak for a poster.
SoundCloud. The friendliest of the streaming targets. Tracks play in a browser without an account, and the URLs are short, which keeps the grid small.
Podcast episodes. Link the episode page on your host (Buzzsprout, Transistor, Libsyn) rather than an Apple or Spotify deep link. The host page plays in any browser, has no login wall, and usually carries the show notes.
Google Drive and Dropbox. Set sharing to “Anyone with the link” before printing anything. The classic failure is a code that works perfectly for you because you are signed in, and shows a permission wall to everyone else. Test it in a private window on a phone that is not yours.
A direct MP3 URL. Opens the browser’s bare audio player. It works, there is nothing to look at, and on some Android browsers it downloads instead of playing.
Shorter links make smaller, more scannable codes
Every character you encode adds modules to the grid, and more modules means smaller squares at the same printed size. Measured against the ISO capacity table:
| Link | Length | At level M | At level H |
|---|---|---|---|
| Direct MP3 URL | 40 bytes | 29x29 | 37x37 |
| ScreenApp share link | 44 bytes | 33x33 | 37x37 |
| SoundCloud track | 48 bytes | 33x33 | 41x41 |
| Spotify track | 53 bytes | 33x33 | 41x41 |
| Apple Music track | 66 bytes | 37x37 | 49x49 |
| Google Drive file | 81 bytes | 37x37 | 49x49 |
An Apple Music link at H needs a 49x49 grid where a SoundCloud link needs 41x41. Printed at the same 25mm, that is roughly 0.44mm per square against 0.52mm, and the small end is where older phone cameras start to hesitate. Strip tracking parameters like ?i= tails and utm_ before you generate. They cost you modules and buy nothing on paper.
Error correction levels and print sizing work identically for audio and video, so rather than repeat it here, the full breakdown with the scan-distance table is on the video to QR code generator.
Where audio QR codes actually earn their keep
A code beside the exhibit label replaces a rented handset and its cleaning, charging, and stock problems. Visitors use their own phone and their own headphones. This is the use case where the silent-switch warning on the label matters most.
A recorded voice or a favourite song, reachable from an engraved code. Nothing on this page has a longer print life, so point the code at a URL on a domain you control rather than a streaming service that may reorganise its links.
A voice message inside a card, or the first-dance track on a place setting. Small print area, so keep the URL short and the error correction at H, since cards get handled hard.
A code on a worksheet or flashcard opens the native-speaker recording. Pair it with a transcript so learners can read and listen together, which is the whole point of the exercise.
An audio version of a menu, leaflet, or safety notice for visitors who cannot read the print. Worth pairing with large-type instructions, because a small unlabelled code is itself an accessibility barrier.
Spoken setup instructions for a product whose printed manual nobody reads. Audio beats video here because people can listen while their hands are busy with the thing they are assembling.
The page behind the code matters more for audio than for video
You can skim a video by dragging the scrubber and watching thumbnails go by. Audio gives you nothing. A 40-minute recording behind a bare play button is a wall, and a listener who wants one fact has to hunt for it in real time.
That is why the landing page does more work here. Point the code at a ScreenApp share link and the scan opens the audio plus a full transcript, an AI summary, and chapters, in a mobile browser with no app and no account. Someone can read the summary in fifteen seconds, search the transcript for the part they need, or listen properly with captions.
For a training recording, a lecture, a podcast episode, or an interview, that is the difference between a code people use once and one they come back to. To get that link, drop your file into the uploader tab above, or read the walkthrough on the video to link converter. The free plan covers one recording and needs no card to sign up. Continuing past that needs the 7-day trial, which does need a card to start, or Pro at $19/month billed annually.
Need the words rather than the sound? The audio to text converter handles transcription on its own, and audio to SRT produces subtitle files.
