Try It: JSON Payload Size Estimator

Try It: JSON Payload Size Estimator

animation
sensing
power-management
Try Keep Number of sensors at 5, Average key name length at 11, and Average value length at 6; increase Readings per payload from 1.
Observe With Include timestamp field checked, the opening single reading and buffered payload both show 137 bytes.
Explain Average key name length and Average value length are added to fixed punctuation allowances for each field, then the timestamp and outer braces are counted.

Technical boundaries. The estimator assumes one byte per counted text character, a fixed 30-byte timestamp contribution, and 96 readings per day. Arrays add separators and wrappers; transport headers and radio energy are excluded, so buffering need not reduce the displayed payload bytes.

NoteTry It: JSON Payload Size Estimator
Single reading
Buffered payloadArray of objects
Daily TX data for 96 readings/day:

Estimate assumes JSON text encoding. Actual size varies with value precision and key names. LoRaWAN max payload: 242 bytes; MQTT typical max: 256 KB.

Back to the chapter