Image credit: AI-generated using OpenAI (ChatGPT / DALL·E)
Picture this. It's late afternoon, the episode is finally mixed, and the client wants it before they log off. You hit send and the email bounces. Attachment too large.
Nothing about that is dramatic, yet it can sour a working relationship fast. And if you're a freelancer or run your own show, there's nobody else to blame or to fix it. You're the engineer, the producer and the person answering emails.
That's why file formats deserve a bit of your attention. Women building careers in podcasting, voiceover and sound design often work solo or in small teams, and small habits are what make a solo operator look dependable.
Learning the technical side of audio production also builds something valuable: confidence in making decisions, communicating with clients and taking ownership of projects. Whether you're entering the industry, growing a freelance business or managing a production team, knowing how to handle audio files is a practical professional skill.
This guide covers WAV versus MP3, when to use which, and a few mistakes worth dodging.
Why this matters more than it seems
We tend to file "technical stuff" and "professional reputation" in separate boxes. They aren't separate. A client who can't open your file doesn't think "wrong format." They think "hard to work with."
Remote work raises the stakes. Your voice actor might be in one city, your editor in another, your client on a train with a patchy signal. Everyone is listening on a different device, and most of them are listening on a phone. Picking the right file for the right moment keeps feedback flowing and keeps the project in your hands.
For women establishing themselves in audio technology, these technical decisions also create opportunities to demonstrate expertise. Understanding the requirements behind a file delivery makes it easier to explain your workflow, recommend practical solutions and manage expectations.
You don't need to know every audio specification by heart. Knowing which questions to ask, and why the answers matter, is a strong starting point.
WAV in a nutshell
The WAV file format was developed by Microsoft and IBM and is built on a structure called RIFF, the Resource Interchange File Format. Usually a WAV file holds uncompressed PCM audio. In that form, the audio data is preserved without lossy compression, giving editors access to the full recorded signal.
That's why editors love it. Noise reduction, EQ and compression generally benefit from working with the highest-quality available source. The catch is size.
A stereo file at 16-bit/44.1 kHz runs at about 1,411 kbps, roughly 635 MB an hour. Bump it to 24-bit/48 kHz and you're at 2,304 kbps, close to 1 GB an hour.
So a single hour-long interview can be about a gigabyte before you've cut a word. Fine for a studio drive. Not fine for email.
WAV is particularly useful when recordings will pass through several stages of production. Keeping the original audio in a high-quality format gives editors more flexibility and avoids unnecessary losses from repeated encoding.
MP3 in a nutshell
MP3 (MPEG-1 Audio Layer III) came out of work involving the Fraunhofer Institute in the early 1990s.
It's lossy. The encoder quietly drops details that human hearing is least likely to catch, such as quiet sounds hiding behind louder ones.
The payoff is size. One hour of stereo at 320 kbps comes to about 144 MB, and at 192 kbps about 86 MB. For many spoken-word review copies, that's plenty.
Figure 2: Approximate size of one hour of stereo audio by format. Original illustration created for this article (author's own work).
But "lossy" means exactly that. Once the detail is gone, it's gone. Almost every rule below comes from that one fact.
MP3 files are convenient for sharing finished material, particularly when recipients need a quick download rather than a file for further professional editing.
Image credit: AI-generated using OpenAI (ChatGPT / DALL·E)
So which one, and when?
Think about where you are in the project.
While you're recording, editing and archiving, stay with WAV whenever possible. The same goes for anything you're handing to a mastering engineer or another editor who'll keep working on it.
When the file is only going to be listened to, such as a rough mix, an audition or a final episode headed to a host that accepts MP3, switch to MP3.
The one thing I'd never do is go backwards unnecessarily. If you've got the original WAV, don't edit or master from an MP3 instead. Repeated rounds of lossy encoding can introduce additional artifacts, and converting an MP3 back to WAV won't restore the information already removed.
For freelancers, agreeing on delivery formats at the beginning of a project also prevents confusion later. A simple conversation about file requirements can save revision time and make collaboration easier.
Three situations you might recognise
The voice actor on a deadline. You've recorded an audition in 24-bit WAV, tidied the breaths and mouth clicks, and the casting contact wants it within the hour. Many mail systems cap attachments somewhere around 20 to 25 MB, so a long WAV may get bounced. A short read as a 192 kbps MP3 will often be easier to deliver, and your original stays safe for the final handoff.
The indie podcast host. You record a conversation in WAV so you can clean the background noise properly. Once the episode is locked, you export an MP3 for your hosting platform, provided it meets the platform's specifications. Listeners get something that downloads quickly on mobile data, and you still hold the full-quality version for clips later.
The sound designer on a film. A director wants to hear your draft ambience on their commute. Sending a full session isn't realistic. A small reference file gets you a reply sooner, and the big files wait for the final handoff.
Same idea each time: full quality while you work, small files while you collaborate.
These examples also reveal an important career skill: understanding the needs of different collaborators. Technical competence isn't only about operating software. It's about delivering work in a format that allows everyone else to do their job efficiently.
Converting without wrecking the sound
Your editing software can do the conversion, but an online tool is handy when you're away from your main setup. If you just need to convert wav to mp3 quickly, pick one that lets you choose bitrate and channels yourself instead of forcing one default.
Before uploading audio to an online converter, check whether the recording contains confidential client material. For sensitive projects, exporting directly from your editing software may be the better option.
A few habits that help, whatever tool you use:
Match bitrate to the job. 320 kbps is a safe pick for high-quality music delivery when MP3 is required. 192 kbps is generally fine for many spoken-word purposes, depending on the material and delivery requirements.
Keep mono recordings mono when appropriate. If your source is a single mono voice, there's often no reason to create a stereo file. This helps avoid unnecessary file size.
Listen to the result before sending. Check representative sections, including the loud parts and the quiet ending, to catch obvious problems.
Name files clearly. "Episode12_v3_review.mp3" beats "final_final2.mp3" every time.
Confirm the delivery specifications. Some clients and platforms require particular formats, sample rates or loudness settings. Follow those requirements rather than relying on a single export preset.
These habits don't take much time, but they help make your workflow predictable and professional.
Image credit: AI-generated using OpenAI (ChatGPT / DALL·E)
Check your peaks first
One technical snag is worth knowing. When audio is encoded to MP3, the decoded signal can occasionally peak a touch higher than the original. If your WAV was pushed right up to 0 dBFS, that can sometimes result in distortion during playback.
A common precaution is to leave a little headroom, often targeting around -1 dBTP (decibels true peak), depending on the delivery requirements. Platforms may publish their own loudness and peak guidance, so check the requirements of wherever your audio is going, for example the Apple Podcasts audio requirements.
Dithering often gets lumped into this topic, so a quick clarification: dither is used when you reduce PCM bit depth, say from 24-bit down to 16-bit. That's about preparing a lower-bit-depth PCM file, not a necessary step simply because you're creating an MP3.
Understanding details like these becomes easier with practice. You don't need to master every technical concept immediately. Learning one part of the production process at a time builds a useful foundation.
Building confidence through technical skills
Audio production combines creative judgment with technical problem-solving. As your career develops, being comfortable with both can give you more independence in your work.
For women pursuing careers in podcasting, sound engineering, voiceover production or digital media, file management is one of many practical skills that support professional growth.
Knowing why you use WAV for editing and MP3 for sharing helps you make informed decisions instead of relying entirely on someone else's instructions.
It also improves collaboration. When a client asks for a smaller file, you can explain the trade-off between file size and audio quality. When another editor requests the original recording, you understand why that matters.
These conversations can help establish trust, particularly when you're managing projects independently or taking on greater technical responsibility.
Sharing what you've learned with colleagues and newer professionals adds another dimension. A simple explanation of file formats may help someone else avoid a frustrating delivery mistake or feel more comfortable with an unfamiliar production workflow.
Technical confidence grows through experience, curiosity and practice. It doesn't require knowing everything from day one.
Habits that make you easy to work with
Nobody gets praised for tidy file management, but people notice when it's missing.
Keep an untouched copy of every original recording. Store your masters in two separate, reliable locations. Say clearly whether a file is a review copy or a final. And ask what format the client or platform needs before you export, not after.
For longer projects, consider establishing a simple folder structure for original recordings, working sessions, review exports and approved masters. That makes it easier to locate the right version when a client requests changes months later.
Documenting your workflow also helps if you eventually collaborate with other producers, editors or assistants. Clear processes make it easier to share responsibilities without losing track of important files.
None of this needs an engineering degree. It needs a routine, and anyone can build one.
Keep learning
If you're early in an audio or podcasting career, the technical side can feel like a lot, especially when you're one of few women in the room.
Most of it is learnable in small steps, and each step makes your work a little more reliable.
Understanding audio formats is only one piece of a larger professional skill set. Over time, developing confidence with recording, editing, troubleshooting and client communication can open doors to more complex projects and greater responsibility.
The goal isn't to become an expert overnight. It's to keep building skills that make your work stronger and give you more control over your career.
For more on building skills and confidence in tech careers, explore the resources at WomenTech Network.
FAQ
Does converting WAV to MP3 change pitch or tempo?
No. A correctly performed conversion preserves the original pitch and tempo. What changes is how the audio information is stored, with MP3 using lossy compression to reduce file size.
What's the best format to send to a mastering engineer?
Send the full-resolution WAV whenever it's available, unless the engineer specifies another format. Mastering generally works best with the highest-quality source you have.
Can I turn an MP3 back into a WAV to get the quality back?
You can change the file type, but you can't restore the audio information that lossy compression removed. Always keep your original WAVs.