Measure a FLAC file's loudness to EBU R128 and adjust it to a target such as -14 LUFS for streaming. Runs entirely in your browser — the audio never leaves your device.
Detailed side-by-side format architecture for Free Lossless Audio Codec (.flac) and Free Lossless Audio Codec (.flac). Every conversion executes strictly within isolated browser memory without network transit.
Drag and drop your .flac file onto the working surface or use the system file dialog. File magic bytes are verified locally on device.
Select a quality preset (Lossless, Visually Lossless, Balanced, Smallest) or adjust advanced encoding switches in the options panel.
Click CONVERT to execute local WebAssembly compilation. Save the finished .flac directly to local storage, or stage it for chaining.
Prefer local shell scripting? Run this standard POSIX command on your machine to achieve equivalent transcoding without a web interface:
# Convert FLAC to FLAC locally
ffmpeg -i input.flac -codec:a flac output.flacTrim a FLAC file
Working with files across multiple web pages? The official convrtr Chrome Extension adds native Side Panel docking, right-click context menu media extraction, and visible viewport capture. Powered by the same zero-upload client-side WebAssembly engine.
LUFS measures how loud something actually sounds, not how tall its waveform is. Peak normalisation sets the loudest instant to full scale, which tells you nothing about perceived loudness — a sparse acoustic track and a dense compressed one can share a peak and differ enormously in how loud they seem. LUFS follows ITU-R BS.1770: the signal is filtered to approximate the ear's sensitivity, measured in 400ms blocks, and quiet passages are gated out so silence does not drag the figure down.
Because getting there would have clipped the peaks. If a track needs +11dB to reach -14 LUFS but only has 8dB of headroom, the remaining 3dB has nowhere to go and the loudest moments would distort. convrtr applies what fits, tells you how far short it fell and why. Clipping cannot be undone; being 3dB quiet can.
No, and it cannot be. Normalising multiplies every sample and rounds the result, so the file is not bit-identical to the original — that is inherent to changing loudness rather than a shortcut being taken. The rounding error sits around -96dB at 16-bit, far below audibility, but this catalogue distinguishes 'inaudible' from 'identical' and so should you. Keep the original.
No. convrtr has no server that receives files. Everything runs in your browser, and you can confirm it by opening your network tab — or by going offline first.
Free Lossless Audio Codec (FLAC) and Free Lossless Audio Codec (FLAC) serve distinct roles across the digital workflow. Converting to FLAC provides optimized compatibility, modern compression efficiency, or standardized playback across web browsers, operating systems, and media production environments.
The output format (FLAC) is inherently lossless or supports lossless operation. Your original visual or audio fidelity is mathematically preserved without quantization artifacts.
Never. convrtr is architected with a strict zero-upload model. All processing, decoding, decompression, and encoding happen 100% locally on your machine using sandboxed WebAssembly and Web Workers. Your data never touches an external server, database, or analytics collector.
You can execute this conversion locally via command-line utilities such as ffmpeg, cwebp, or ImageMagick. For example: see the developer terminal recipe provided in the technical specifications dossier above. convrtr provides the identical local-first capability directly inside your browser without installing CLI packages.
Yes. You can drop multiple .flac files into the instrument to process them concurrently in browser Web Workers, or click 'Open in Master Studio' to queue mixed formats, configure individual targets, and export as a single ZIP archive.
Convert web media, local files, and document assets directly in Chrome Side Panel using client-side WebAssembly, zero-server uploads, and the official convrtr browser extension.
A byte-level walkthrough of the MLW container format: the Root marker, the filename block, the AES-GCM payload, and the one part of the layout nobody has documented.
MLW uses a single fixed encryption key shared across every install of the app. What that means for whether unwrapping it counts as DRM circumvention — in plain English, not legal advice.