Add your BSON file
Drop one or more .bson 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.
Converting a .bson font to .yaml repackages the same glyphs and metrics for a different delivery target. Free, private, and validated — the file never leaves your browser.
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.Converting a .bson font to .yaml repackages the same glyphs and metrics for a different delivery target. A .bson file holds BSON: the binary document format MongoDB stores and transmits. It looks like JSON with types added — every field is length-prefixed and carries a type byte — which makes documents skippable during a scan and gives them an ObjectId, a real date type, and 32- and 64-bit integers distinct from doubles.
A .yaml file stores structured data in YAML, a syntax that uses indentation rather than brackets to express nesting. Its readability made it the configuration language of the DevOps era — Kubernetes manifests, CI pipelines, and Ansible playbooks all live in .yaml files. For this route the practical draw is exceptionally readable for nested configuration and comments are supported, unlike JSON — balanced against whitespace sensitivity makes both hand-editing errors and machine generation fiddly, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .bson, often larger than the equivalent JSON, because of length prefixes and field names repeated per document. Switching to .yaml buys you exceptionally readable for nested configuration, which is why it is the better fit for kubernetes resource manifests and Helm charts. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | BSON (.bson) | YAML data (.yaml) |
|---|---|---|
| Format type | Lossless — every pixel or sample is preserved exactly | Text-based — characters and structure, so there is no visual quality loss |
| How it stores data | a document is a little-endian int32 total length, a sequence of typed elements, and a terminating null byte | indentation with spaces (tabs are forbidden) expresses structure, with no closing delimiters at all |
| Strongest at | inspecting a mongodump export without restoring it to a database | kubernetes resource manifests and Helm charts |
| Weak spot | often larger than the equivalent JSON, because of length prefixes and field names repeated per document | whitespace sensitivity makes both hand-editing errors and machine generation fiddly |
Drop one or more .bson 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.
Select .yaml in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if YAML is selectable, the route is real and validated.
Press Convert. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid YAML file. Outputs keep the original filename with the .yaml extension.
There is no visual quality to lose — bson is lossless-oriented and yaml is text-oriented, so the question is structural fidelity. Text, ordering, and basic structure are preserved; complex layout, embedded objects, and styling beyond the target's model are simplified.
Yes — the .bson file is processed inside your browser tab and never uploaded. The font tables are parsed and rewritten locally with fonteditor-core; glyph outlines, hinting, and kerning survive the trip. Close the tab and the file is gone from memory.
Every major language has a solid YAML library — PyYAML, js-yaml, go-yaml — and modern editors provide highlighting, folding, and schema-aware linting. Operating systems have no native viewer beyond text editors, which is all the format needs.
It depends on the content: indentation with spaces (tabs are forbidden) expresses structure, with no closing delimiters at all. Convert one representative file first and compare before batch-processing a large set.
In .bson, type information is preserved through the conversion summary; JSON, CSV and spreadsheet targets record BSON-specific types as their documented string representations. 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.