Description
Inspect Base32 tail pad bits from a byte-count remainder.
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.
Inspect Base32 tail pad bits from a byte-count remainder.
When to use this tool
Use Base32 Last Symbol Padbits when inspecting one stated alphabet, group or padding component.
How to use the tool and how it works
- Enter symbolValue, byteRemainder. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read unusedBits, unusedValue, canonical. Inspect canonical before interpreting the associated values.
Inspect Base32 tail pad bits from a byte-count remainder. Require symbolValue in [0,31] and byteRemainder in [0,4]; use unusedBits [0,2,4,1,3], mask low bits and flag zero unusedValue.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 |
|---|---|---|
| symbolValue | Symbol Value | Required. Safe integer; minimum 0; maximum 31. |
| byteRemainder | Byte Remainder | Required. Safe integer; minimum 0; maximum 4. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| unusedBits | Unused Bits | Required. Safe integer. |
| unusedValue | Unused Value | Required. Safe integer. |
| canonical | Canonical | Required. Boolean. |
{
"input": {
"symbolValue": 16,
"byteRemainder": 1
},
"output": {
"unusedBits": 2,
"unusedValue": 0,
"canonical": true
}
}Limitations and assumptions
- Remainder is supplied, not derived from a stream; written equals padding is not inspected.
- 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
-
Calculation and input contract: decode/base32-last-symbol-padbits — tool.io
-
RFC 4648: Base-N encodings — RFC Editor
Similar or alternative tools
- Decoding: Base32 Final Symbol Pad Bits Check
Check Base32 final-symbol canonicality under an explicit tail count.
- Base N Leading Zero Symbol Count
Count and remove leading occurrences of a supplied zero symbol.