> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/references/database-information-and-organization/binary-prefixes.md).
# Binary prefixes
The way binary sizes are represented depends on which standard is followed. According to the IEC standard:
* 1 KB equals 1000 byte**s**
* 1 MB equals 1000 KB
* 1 GB equals 1000 MB
It is a decimal-based system commonly used by Apple when reporting disk capacities.
In contrast, the JEDEC standard, widely adopted by Microsoft and many other vendors, defines:
* 1 KB as 1024 bytes
* 1 MB as 1024 KB
* 1 GB as 1024 MB
This binary interpretation aligns with the way RAM and Microsoft Windows report capacity.
Nexthink adopts an approach that is familiar to the majority of its users. When querying or exporting data, it interprets 1 KB as 1024 bytes, 1 MB as 1024 KB, and 1 GB as 1024 MB, thus following the binary (JEDEC) model. However, it labels these binary values using the decimal symbols KB, MB, and GB, rather than the IEC’s binary-specific units (KiB, MiB, GiB).
This ensures consistency with Microsoft’s conventions and common user expectations for memory-related values. Although it may lead to apparent discrepancies when compared with Apple’s IEC-based reporting of disk capacities, these differences are only in labeling; the underlying byte counts remain exactly the same.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.nexthink.com/references/database-information-and-organization/binary-prefixes.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
