Description
Convert supplied record-storage size between decimal and binary units.
Administrative records distinguish delegated authority, sign-off assertions, conditional fields, counter-minutes and date boundaries. A half-open delegation period excludes its final date, and staffed-counter time can sum simultaneous counters. Local flags and fees do not authenticate an approval or establish lawful authority or adequate service.
Convert supplied record-storage size between decimal and binary units.
When to use this tool
Use Records File Volume Unit Crosswalk when you already have amount, inputUnit, outputUnit and need to convert supplied record-storage size between decimal and binary units.
How to use the tool and how it works
- Enter amount, inputUnit, outputUnit. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read amount. Use the output convention below.
Require amount>=0 and units MB, GB, MiB or GiB; convert through factors 1000000, 1000000000, 1048576 and 1073741824 bytes.1
Mebi and gibi denote binary multiples, while mega and giga denote decimal multiples. A byte-based storage conversion must retain that distinction rather than treating MB and MiB as interchangeable.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| amount | Amount | Required. Finite number; minimum 0. |
| inputUnit | MB/GB use powers of 1000; MiB/GiB use powers of 1024. Units are bytes, not bits. | Required. Text; maximum UTF-16 length 8192. |
| outputUnit | Output Unit | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| amount | Amount | Required. Finite number. |
{
"input": {
"amount": 1,
"inputUnit": "GiB",
"outputUnit": "MiB"
},
"output": {
"amount": 1024
}
}Limitations and assumptions
- These are bytes rather than bits, with SI decimal and IEC binary prefixes. No file is read, compression estimated, storage allocated or actual size verified.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Check controlled policies, original case records, verified roles and account definitions. Apply complete administrative and legal processes when local routing delays, document counts or supplied approval comparisons cannot determine a valid action.
References
Similar or alternative tools
- Paperwork Attachment Page Count
Sum supplied main-document and attachment page counts.
- Record Routing Return Hop Delay
Add supplied outbound and return routing delays.