If you are a visitor wondering what the ".jb64" file extension is, then you've come to the right place to learn more about this file format. If you are looking for something to download to be able to process a ".jb64" file that someone sent to you, check out the JB64 Implementations page.
The JSON-Base64 file format, aka JB64, was invented for performing clean data transfers of database records and spreadsheet values across a wide variety of Internet hosts, software programs, and programming languages. JB64 is encoded in a stream-ready format, follows a clearly defined specification, and the file format and reference implementations are public domain.
JB64 (.jb64) is a serious replacement for the aging CSV (.csv) file format. CSV was invented way back in the 1970's and was never formally defined until October 2005 (35 years too late). As a result, the CSV file format has a number of significant weaknesses as a data transfer file format that only get more apparent as time passes. XML (.xml) was supposed to be the solution, but even XML has its problems. With JSON-Base64, applications that support table-like data (i.e. rows and columns) can send data to each other and encounter far fewer issues that require manual user intervention or custom-built software to handle.
The following is a list of features of the JB64 file format:
- Supports multiple flat field types (booleans, integers, floating-point, strings, etc).
- Preserves Unicode character sequences.
- The first line contains a header record that defines each column name and its type.
- Each line contains exactly one record.
- Can be processed as a stream.
- Optional hash support for detecting accidental data corruption.
- Very easy to implement in most modern programming languages.
- Unencumbered by patents and is public domain.
Files are not intended to be viewed or edited in a text editor other than confirming that the file looks like it is in the JB64 format.
The file format itself is intentionally bloated. Data preservation between applications is deemed much more important than file size. Base64 alone increases data sizes by 33%. If size is a concern, files can be stream compressed after following the specification (e.g. zlib deflate).
The file format is not encrypted. If encryption is desired, a stream cipher may be used to encrypt and decrypt files after following the specification if they will be stored locally or transparently encrypted with SSL/TLS if transmitted over a network.
To encourage the use and implementation of the format, this specification is placed in the public domain via the Creative Commons Zero license. There are no known patents either on the algorithms used or the JSON-Base64 file format.
The various official reference implementations are licensed under MIT or LGPL, your choice.
The original date of release was February 13, 2014.