Convert CUE sheet (.cue) CD-DA audio tracklists, disc images, and chapter metadata into clean, structured JSON with calculated millisecond timestamps in your browser. 100% private with zero server uploads.
Detailed side-by-side format architecture for CUE Document (.cue) and JavaScript Object Notation (.json). Every conversion executes strictly within isolated browser memory without network transit.
Drag and drop your .cue 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 .json 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 CUE to JSON locally
pandoc input.cue -o output.jsonWorking 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.
A CUE sheet is a plain-text metadata file defining how tracks on a compact disc (CD-DA) or disc image (BIN, FLAC, WAV, APE) are laid out, including track durations, pregaps, performers, and titles.
Compact Disc Digital Audio uses a timecode format of MM:SS:FF where FF represents frames at 75 sectors per second. convrtr calculates the exact sector frame count and translates each index mark into precise seconds and milliseconds.
Yes! convrtr parses multi-file references, CATALOG barcodes, ISRC codes, CD-Text data, REM metadata comments, and multiple INDEX positions (such as INDEX 00 pregaps).
Never. All text parsing and JSON generation run entirely inside your browser memory with zero network requests.
CUE Document (CUE) and JavaScript Object Notation (JSON) serve distinct roles across the digital workflow. Converting to JSON provides optimized compatibility, modern compression efficiency, or standardized playback across web browsers, operating systems, and media production environments.
The output format (JSON) 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 .cue 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.