Raw PCM import: supply the missing sample interpretation
A headerless PCM recording does not describe how its bytes should be interpreted. To import it correctly, you need the sample format, byte order where relevant, channel organization and sample rate supplied by its producer. Guessing can produce harsh noise, the wrong duration or incorrect channels even when the file is complete.
Open the relevant downloader · Platform tools and access limits
Obtain the recording description first
Ask the producer for the actual export parameters and whether the payload is truly raw audio. A WAV container can carry descriptive headers; a headerless payload cannot provide the same information by itself. Do not remove a header from a supported container merely because a raw-import option is available in your editor.
Identify whether samples are integer or floating point, their width, and the applicable signedness. For multibyte values, endianness describes the order of bytes within each value. Channel count and arrangement describe how successive values belong to channels. These are interpretation choices, not language selections or audio enhancement settings.
Check the expected size and listening result
For a straightforward interleaved PCM payload, duration can be estimated by dividing byte count by sample rate, channel count and bytes per sample. This estimate assumes no extra framing, padding or attached metadata. A large discrepancy with the producer’s stated duration is a reason to investigate the format rather than trim the recording.
Import a copy with the confirmed parameters and start listening at a low, comfortable level. Stop if the result is unexpectedly loud noise. Compare recognizable speech, beginning and ending, and channel contributions. A readable waveform alone does not prove that byte order or sample interpretation is correct.
Verify an ordinary delivery copy
Export a separate supported audio file once interpretation is established. Inspect its duration, channel count and rate, then listen in the receiving application. A conventional container helps communicate those properties to the recipient, but it cannot make incorrectly decoded samples authentic by labeling them with plausible metadata.
Preserve the original payload together with the producer’s parameter note. If essential details remain unknown, describe the file as unresolved rather than distributing a guessed decoding as a verified recording. This downloader handles supported source media; it does not identify arbitrary raw recordings or guarantee recovery from missing format information.
Worked example
Suppose a producer confirms 48,000 Hz, mono, signed 16-bit little-endian PCM with no framing. Two bytes per sample imply 96,000 bytes per second. A 5,760,000-byte payload therefore represents sixty seconds. Treating the same bytes as stereo would suggest thirty seconds, showing why the channel description matters before editing.
Related guidance
Sources and verification
Reviewed 2026-10-09. Product behavior is limited to available source formats and provider access; it is not a promise that every public link works.