free · in-browser · no upload
Drop your CBOR file. We'll convert it to JSON right here in your browser, your file never leaves your device.
Select your file here to get started
or drop your file here.
Accepts .cbor, .bin
How it works
Click the dropzone above or drag a CBOR from your desktop. Files of any size, there's no upload, so there's no upload limit.
The conversion runs entirely in this tab using JavaScript and WebAssembly. Your file never touches our servers, we don't have any.
Get your JSON the moment the conversion finishes. Convert another, or close the tab.
Your file is never uploaded. The entire conversion runs in your browser using WebAssembly. We can't see what you convert because we have no server to see it.
Server converters cap free users at 1-2 GB and gate larger files behind a paid plan. Since nothing uploads, our limit is whatever your browser can handle.
No account required. No watermark on the output. No queue. Drop a file, get a converted file.
Why convert CBOR → JSON
CBOR (RFC 8949) is the IETF-standard binary JSON, the encoding underneath COSE, WebAuthn attestation, and most modern IoT protocols on CoAP / LwM2M. To audit or modify a captured payload you usually want plain JSON; this decodes it with base64 for embedded byte strings.
You captured a WebAuthn attestation statement and want to read the authenticatorData fields. Save the CBOR bytes, drop here, inspect the decoded JSON.
Decoded JSON shows $binary wrappers everywhere.
CBOR distinguishes byte strings from text strings (JSON does not). We wrap byte strings as { "$binary": "<base64>" } so you can round-trip cleanly. If you only need the text view, post-process to decode the base64 back to the original strings.
Formats involved
CBOR is a file format we support converting. Detailed format information is being added, for now, drop your file in the converter above and you'll get the conversion you came for.
How to open
Most operating systems open this format with a default application; if not, search for a free reader/viewer for the format.
JSON is a lightweight text format for structured data, nested objects, arrays, strings, numbers, booleans. It's the lingua franca of web APIs, configuration files, and data interchange between programs. Human-readable when formatted, machine-parseable in every programming language, and roughly half the size of equivalent XML.
How to open
Any text editor reads JSON. Browsers display .json files in a formatted tree view. VS Code and similar editors highlight syntax.
You may also need
Related tools
FAQ
Yes. No signup, no watermark, no daily file count limit. Every conversion runs in your browser, your file never touches our servers because there are no servers.
Nowhere. The conversion runs entirely in your browser using JavaScript and WebAssembly. Your file is never uploaded to our servers. We don't have any servers handling files, there's nothing for us to log, store, or accidentally leak.
Whatever your browser can hold in memory. Practically, this means a few hundred MB on most computers, significantly larger than the 1-2 GB caps that server-upload converters charge for. Very large files (multi-GB) may require closing other browser tabs first.
File interchange. API responses, configuration files, structured data interchange. The most common reason to convert is compatibility, JSON works in places where CBOR doesn't, or vice versa.
Most operating systems open this format with a default application; if not, search for a free reader/viewer for the format.
Once the page is loaded, the conversion itself runs entirely offline. The first time you use a tool, your browser downloads the conversion library (a one-time cache). If you reload while offline, the page won't load, but you can install the site as a Progressive Web App for full offline use.
Single file at a time for now. Batch conversion is on the roadmap, for now, drop one file, download the result, then convert the next.
