Published by PitchChanger · Updated · How these guides are made
How to use this workflow
Identify the receiving application
Ask for the application or upload service and the action they need to perform: listen, edit, import into a video project or submit through a form. If there is a published delivery specification, request its exact link or text. An extension alone does not settle every compatibility question.
Agree a short test before the full delivery
For a new destination, propose a short, non-sensitive sample using the agreed settings. Ask the receiver to open it in the actual destination and report the result. Do not treat successful playback on your own device as proof that their upload service or editor accepts it.
A receiver questionnaire that separates requirements from preferences
Copy the questions below into your own delivery note. They are an original suggested intake form, not requirements imposed by a particular service. Record “not specified” when an answer is missing and resolve anything that could block delivery before preparing a long batch.
Swipe or scroll sideways to read all columns.
| Question | Why it matters | Example answer to clarify |
|---|---|---|
| Where will you use the file? | Identifies the real decoder or upload check | A named desktop editor, not merely “my computer” |
| Which container and audio codec are accepted? | Container and encoded audio are separate choices | PCM audio in WAV, if specified |
| Required sample rate and channel layout? | A project can impose a technical constraint | 48,000 Hz; stereo; confirm both |
| Bit depth or bitrate requirement? | These describe different encoding choices | 16-bit PCM or 192 kbps MP3; do not interchange |
| Maximum bytes or duration? | A valid format can still exceed a limit | Exact limit and MB/MiB meaning |
| Do you need to edit or only listen? | Changes which delivery is useful | Editable source separately from review copy |
Turn a vague request into an explicit agreement
Invented request: “Please send something small that I can review on my phone.” It does not establish a codec, a byte cap or whether the receiver needs editing material. Ask those questions instead of silently turning “small” into a quality setting.
A hypothetical completed agreement might read: “Review only, MP3 accepted, stereo, 44,100 Hz, 192 kbps; maximum 10,000,000 bytes per file; the original is delivered separately if edits are requested.” These are example choices, not universal phone requirements or a recommendation for every recording. The receiver should confirm them for the actual destination.
For a 180-second clip at a constant 192,000 bits per second, payload arithmetic gives 192,000 × 180 ÷ 8 = 4,320,000 bytes. Container metadata and encoder behavior affect the actual file size; inspect the final download rather than promising an exact total from this estimate.
Resolve incompatible requests before choosing settings
If the receiver asks for settings outside the available converter controls, say so before exporting. This converter offers MP3, WAV, FLAC, AAC, OGG, AIFF and ALAC, with output-specific rate and quality controls. It does not offer every codec or every possible rate; do not rename an extension to imitate an unsupported format.
If the receiver cannot name the codec, ask them to test the proposed short sample. A successful test establishes that sample on that destination at that time. It does not certify every file, browser version or future upload. Record the application, date and agreed settings with the acceptance note.
Use the agreed answer to prepare the file
Once the specification is clear, choose the actual available converter settings, export and inspect the saved file. Keep the agreed requirements beside it. The separate validation guide explains how to translate an existing specification into checks; this page is the conversation that makes that specification possible.
Common questions
Is WAV always the safest thing to send?
No single delivery choice fits every destination. WAV can suit editing, while a review service may impose a different format or byte limit. Ask what the receiving application accepts, and keep an unchanged source regardless of the review format.
Can I just change .m4a to .mp3?
Changing a filename extension does not convert the encoded audio. Choose an actual supported conversion when required, then test the downloaded result. Ask for the codec as well as the container when the destination has a strict specification.