Add your PARQUET file
Drop one or more .parquet files onto the converter above, or browse for them. They load into browser memory only. Nothing is uploaded, so there is no size-based pricing and no server queue.
PARQUET to CBOR
Restructuring .parquet data as .cbor changes the serialization without touching the values themselves. Free, private, and validated: the file never leaves your browser.
Private for supported formats, processed in your browser
Runs on your deviceConvert supported files
Drop PARQUET files here
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.About converting Apache Parquet to CBOR
Restructuring .parquet data as .cbor changes the serialization without touching the values themselves. A .parquet file is a self-describing columnar dataset: values from the same field are stored together so an analytics engine can read only the columns and row groups a query needs. It is designed for compact long-term storage, unlike Arrow IPC, which is optimized for immediate in-memory access.
A .cbor file holds Concise Binary Object Representation data: a binary format built on the JSON data model but standardized by the IETF, with a tag mechanism that lets it carry dates, big integers, decimals and arbitrary application types without inventing a convention for each one. For this route the practical draw is an actual IETF standard with a stable, versioned specification and tags express types JSON cannot, without breaking decoders that ignore them, balanced against tag semantics are only as portable as the two ends' agreement on them, which is worth knowing before you commit a large batch.
Why convert PARQUET to CBOR?
The practical trigger for this conversion is usually a mismatch: with .parquet, not human-readable and awkward to modify in place. Switching to .cbor buys you an actual IETF standard with a stable, versioned specification, which is why it is the better fit for WebAuthn and FIDO2 attestation and assertion payloads. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
PARQUET vs CBOR at a glance
| Aspect | Apache Parquet (.parquet) | CBOR (.cbor) |
|---|---|---|
| Format type | Lossless: every pixel or sample is preserved exactly | Lossless: every pixel or sample is preserved exactly |
| How it stores data | columns are split into row groups and pages, allowing a reader to skip both irrelevant columns and ranges of rows | every item begins with a major type in the top three bits and a length or value in the remaining five, which makes decoders small enough for microcontrollers |
| Strongest at | storing analytics tables in a data lake or object store | WebAuthn and FIDO2 attestation and assertion payloads |
| Weak spot | not human-readable and awkward to modify in place | tag semantics are only as portable as the two ends' agreement on them |
| Metadata | the schema, logical types and column names are read. Key-value metadata is reported where relevant, but CSV cannot carry it and spreadsheets preserve only the displayed table rather than Parquet's physical encodings and statistics | semantic tags are read and reported; JSON and YAML targets receive their normalized textual form, since neither has a tag mechanism |
Pick CBOR as the output
Select .cbor in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if CBOR is selectable, the route is real and validated.
Convert on your device
Press Convert. The restructuring is plain local parsing, and your data is never posted to a server for processing.
Verify and download
Each result is checked before the download unlocks: where CBOR has a signature or a structure this converter can read back, the file is re-opened and parsed, and where it has neither, the check is that a non-empty file of the declared type came back. A result that fails is reported as an error instead of being offered for download, and outputs keep the original filename with the .cbor extension.
PARQUET to CBOR questions, answered
Will converting PARQUET to CBOR lose quality?
Since parquet is lossless-oriented and cbor is lossless-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .cbor itself requires.
Is it private to convert PARQUET files here?
Yes. The .parquet file is processed inside your browser tab and never uploaded. The restructuring is plain local parsing, and your data is never posted to a server for processing. Close the tab and the file is gone from memory.
Where will the CBOR file work?
Libraries are widely available for C, Rust, Go, Python, Java, JavaScript and .NET, and browsers speak CBOR indirectly through the WebAuthn API. Novus Convert normalizes .cbor locally into a JSON-compatible model and writes JSON, CSV, XLSX, YAML or YML. Tagged values that JSON cannot represent are converted to a documented textual form rather than being silently discarded.
Will the CBOR file be bigger or smaller than my PARQUET?
It depends on the content: every item begins with a major type in the top three bits and a length or value in the remaining five, which makes decoders small enough for microcontrollers. Convert one representative file first and compare before batch-processing a large set.
What happens to the metadata in my PARQUET file?
In .parquet, the schema, logical types and column names are read. Key-value metadata is reported where relevant, but CSV cannot carry it and spreadsheets preserve only the displayed table rather than Parquet's physical encodings and statistics. Re-encoding through the browser pipeline does not carry embedded metadata into the output, which doubles as a privacy scrub. Check the exported file if you specifically need tags preserved.