True peak versus sample peak: verify the final audio delivery
Sample peak reports extrema among stored sample values. A true-peak measurement estimates peaks of the reconstructed signal between those samples using the meter's defined method. The readings can differ, so a sample-peak ceiling alone does not establish compliance with a recipient's true-peak requirement.
Open the relevant downloader · Platform tools and access limits
Identify the meter and the signal being measured
Check whether the meter explicitly reports sample peak or true peak, and record its units and measurement mode. A waveform display or a red overload light is not necessarily a true-peak measurement. Make sure the observed signal comes from the intended output path, including any gain, mix or processing that will be present in the export.
Measure a complete intended delivery when its maximum is the question. A preview of one loud sentence can miss a sharper transient elsewhere. Keep playback volume separate from the file measurement: lowering a device's listening volume makes monitoring quieter without changing the encoded audio values or certifying the stored delivery.
Check the recipient requirement before changing gain
Use the actual receiving specification for the delivery rather than copying an unexplained ceiling from another platform. Peak limits, integrated loudness and allowed format are different requirements. Two recordings can share a peak reading while differing considerably in program loudness. A peak adjustment alone is not a complete loudness workflow.
If peak reduction is needed, decide whether a common gain change or suitable limiting serves the material. Keep the untouched master and listen to the effect on speech, music and short impacts. A meter below a ceiling cannot prove that earlier clipping has been repaired. Also verify whether the chosen limiter supports the measurement objective rather than assuming its name guarantees true-peak protection.
Verify the actual encoded derivative
Measure the saved file after its final encoding, not only the PCM timeline that preceded it. Lossy encoding and later processing can change decoded peaks. Use a meter appropriate to the required standard and include its version or method in the handoff record. FFmpeg's loudnorm documentation distinguishes integrated loudness and true-peak controls; that is a processing reference, not a substitute for identifying the recipient's own acceptance criteria.
Listen to the saved derivative at a sensible monitoring level and confirm its duration, channel arrangement and synchronization. If a recipient converts the file again, the resulting copy needs its own checks; your measurement describes the delivered file you actually assessed. SocialVidDownloader does not expose true-peak mastering or issue compliance certificates. Use an appropriate external audio workflow and keep the report tied to the exact file rather than promising that every later playback or conversion will have the same measurement.
Worked example
Example: an editor observes sample peaks below its chosen ceiling, then exports an AAC review copy. A true-peak meter on that saved copy reports a different maximum. Confirm the recipient's limit, adjust the mastering path if necessary and remeasure the final derivative. Do not label the copy compliant based only on the earlier timeline's sample meter.
Related guidance
Sources and verification
Reviewed 2026-10-12. Product behavior is limited to available source formats and provider access; it is not a promise that every public link works.