What is CSV / BSON Converter?
CSV and BSON Converter places tabular records in MongoDB's binary document format. Encoding wraps rows in an explicit rows document and decoding requires the same contract, preserving table boundaries instead of guessing. ObjectId, dates, and long integers use Extended JSON markers in the intermediate representation rather than unsafe JavaScript numbers. Review the result against the driver version and collection schema. Common workflows include the following. Generate MongoDB driver fixtures. Inspect tabular records in BSON logs. Review dedicated BSON value mappings. The page also documents input boundaries, output behavior, and practical cautions so you can review the result before putting it into an application, configuration, test, or production workflow.
When to use it
- Generate MongoDB driver fixtures.
- Inspect tabular records in BSON logs.
- Review dedicated BSON value mappings.
How to use it
- Choose the delimiter.
- Use unique CSV headers.
- Paste complete BSON Base64 for decoding.
- Review Extended JSON and string typing.
- Load one of the realistic examples first to verify the selected options and processing direction before replacing it with your own data.
- Review the output, status message, and documented limits; copy, download, or continue only after the result matches your expectation.
Runnable examples
The “Example 1” and “Example 2” buttons load the matching inputs. They cover different structures, directions, or boundaries and can be run directly in the workspace.
Example 1
id,name,status
64,CSV BSON,ready
65,CSV Plist,plannedExample 2
SAAAAARyb3dzAD0AAAADMAA1AAAAAmlkAAMAAAA2NAACbmFtZQAJAAAAQ1NWIEJTT04AAnN0YXR1cwAGAAAAcmVhZHkAAAAAInput rules
- CSV headers must be unique.
- BSON must contain one rows array.
- Unsafe values are rejected.
- Text input is counted before processing and is limited to 1,500,000 characters on this page; file modes apply the separate file limit shown in the workspace.
- BSON binary is represented as Base64.
Output rules
- BSON bytes use Base64.
- Dedicated types remain marker objects.
- CSV fields are exported as text.
- Output reflects only the current input, direction, and options; rerun after changing a mode or value instead of treating an earlier result as current.
- Decoded BSON must contain one rows array.
Limitations and cautions
- BSON binary is represented as Base64.
- Decoded BSON must contain one rows array.
- BSON-specific values need destination review.
How your data is handled
All parsing, conversion, Base64 work, and intermediate data remain in the current browser tab. JSONLane does not upload the input or retain it after refresh or close.