Description
Check Base32 final-symbol canonicality under an explicit tail count.
Encoded representations separate alphabet symbols, numerical digit values, byte grouping and tail padding. Recognizing one symbol or pad-bit pattern is not full payload decoding, and different alphabet variants can assign different values.
Check Base32 final-symbol canonicality under an explicit tail count.
When to use this tool
Use Decoding: Base32 Final Symbol Pad Bits Check when inspecting one stated alphabet, group or padding component.
How to use the tool and how it works
- Enter finalSymbol, symbolCount, variant. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read result. Expand result to inspect the returned fields.
Check Base32 final-symbol canonicality under an explicit tail count. Require variant base32/base32hex, a recognized uppercase symbol and symbolCount 2,4,5,7 or 8; unused bits are 2,4,1,3 or 0 respectively.1
Canonical Base-N encodings require unused pad bits to be zero; alphabet membership alone does not establish canonical encoding.2
| Input field | Meaning and units | Accepted input |
|---|---|---|
| finalSymbol | Final Symbol | Required. Text. Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units. |
| symbolCount | Number of data symbols in the final Base32 block: 2, 4, 5, 7 or 8; excludes written equals padding. | Required. Safe integer. |
| variant | Variant | Required. Text; one of "base32", "base32hex". Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| result | Returned object; expand its named members below. | Required. Object. |
| result.unusedBits | Unused Bits | Calculated result member: number. |
| result.canonicalPadBits | Canonical Pad Bits | Calculated result member: boolean. |
{
"input": {
"finalSymbol": "B",
"symbolCount": 2,
"variant": "base32"
},
"output": {
"result": {
"unusedBits": 2,
"canonicalPadBits": false
}
}
}Limitations and assumptions
- The count excludes written padding and must reflect the final group; no complete stream is checked.
- Outputs are nested inside result. 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
Use the complete codec matching the required alphabet and canonicality rules for real encoded data.
References
Similar or alternative tools
- Decoding: Base64 Final Quartet Pad Bits Check
Check canonical pad bits in one standard Base64 quartet.
- Base32 Last Symbol Padbits
Inspect Base32 tail pad bits from a byte-count remainder.