> For the complete documentation index, see [llms.txt](https://odict.gitbook.io/the-open-dictionary-project/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://odict.gitbook.io/the-open-dictionary-project/spec.md).

# File Specification

Compiled odict files are relatively straightforward, as they utilize the [ODict FlatBuffer schema](https://github.com/Nickersoft/odict/blob/master/src/schema.fbs). The buffer generated by this schema take up over 90% of the compiled file, however, addition header information still exists. The table below illustrates the full breakdown of a compiled `.odict` file, in the order in which the values are written to the file. All values written in Little Endian byte order.

| Name         | Type          | Size     | Description                                                                                                           |
| ------------ | ------------- | -------- | --------------------------------------------------------------------------------------------------------------------- |
| Signature    | `CHAR[6]`     | 6        | Signature for the ODict format. Assertions fail if this signature is missing. Should always be `ODICT`.               |
| Version      | `USHORT`      | 2        | Represents the major version of ODict with which the file was created.                                                |
| Content-Size | `ULONG`       | 4 or 8   | Size (in bytes) of the compressed content to read. Used in assertions to validate file length.                        |
| Content      | `CONST CHAR*` | Variable | Snappy-compressed FlatBuffer object. Must be decompressed by Snappy and converted to `uint8_t` before it can be used. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://odict.gitbook.io/the-open-dictionary-project/spec.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.