This LoRaWAN payload converter shows the same bytes as hex, Base64, a byte array and text. Base64 packs every 3 bytes into 4 characters, so the hex 48 65 6C 6C 6F is SGVsbG8= in Base64 and “Hello” as text.
- Hex
–- Base64
–- Byte array
–- Text
–- Length
- – bytes
These bytes are not valid UTF-8 text, so the text line shows printable characters only (· for the rest).
This is not valid for the chosen format: hex needs pairs of 0–9 and A–F, Base64 its 64 characters, and a byte array numbers from 0 to 255.
How it works
How do you convert a LoRaWAN payload from Base64 to hex?
Hex writes each byte as two digits from 00 to FF. Base64 packs every 3 bytes into 4 characters from a 64-character alphabet, with = padding at the end; JSON messages often carry raw payloads this way.
A byte array lists the same bytes as decimal numbers from 0 to 255, as code and some datasheets do. Text reads the bytes as UTF-8; sensor data is usually binary, so expect a few unreadable characters.
The example 01 67 00 E1 02 68 50 is a common sensor layout: channel 1, type 67 (temperature), 00E1 = 225 = 22.5 °C; channel 2, type 68 (humidity), 50 = 80 ÷ 2 = 40 %.
In Hermetry Hermetry’s network server turns payloads into named values with codecs from its library or your own, and downlinks take their data as hex or Base64: The codec library.
Glossary Payload, Codec (payload decoder), Uplink, Downlink
Questions
Questions about the LoRaWAN payload converter
Why do LoRaWAN payloads show up in Base64?
Many network servers and integrations carry the raw bytes as Base64 inside JSON, while device datasheets describe them in hex. Both are the same bytes written differently.
Is my payload sent anywhere?
No. The conversion runs in your browser; nothing is uploaded.
More tools

