Token amount converter

What an atomic amount represents

A token amount usually has a raw integer and a separate display scale. The integer describes atomic units; decimals tells the application where to place the decimal point. For example, 1234567 atomic units at six decimals represent 1.234567 tokens. Neither the symbol nor a rounded dashboard value is a safe substitute for those original inputs.

This converter uses BigInt arithmetic and string operations. It never sends the amount to a server, reads a wallet or calls a blockchain endpoint. The conversion explains a representation; it does not verify the token contract, discover decimals or establish that the input is a real balance. You choose the scale and remain responsible for matching it to the intended asset and observation.

Convert atomic units to a decimal string

Choose Atomic to decimal and enter an unsigned integer without commas, spaces, exponent notation or a sign. The tool divides by ten raised to the chosen decimals and preserves the fractional remainder. It trims unnecessary trailing zeroes in the displayed result while keeping the numerical value exact. No floating-point Number conversion is used for the amount.

Zero decimals leave the amount as an integer. A positive scale can produce a fractional value smaller than one; leading fractional zeroes matter and are retained. For instance, one atomic unit at eighteen decimals is 0.000000000000000001. A display formatter that rounds this to zero has changed the presentation, not the underlying amount.

Convert a decimal string back to atomic units

Choose Decimal to atomic and use a period as the decimal separator. The tool pads the fractional part to the selected scale and joins it with the whole part using integer arithmetic. It rejects extra fractional digits rather than silently round or truncate them. At six decimals, 1.234567 is exact, while 1.2345678 needs a separate rounding policy and is rejected here.

Both directions enforce an unsigned uint256 limit and a bounded input length. Negative reconciliation deltas are a different data type from raw token balances and are deliberately outside this converter’s scope. The scale must be an integer between zero and 255. A permitted scale in the tool does not claim that every token standard or product integration accepts it.

Preserve exactness after conversion

Keep atomic quantities as integer strings through JSON, database drivers and exports. Converting a large integer to JavaScript Number can lose digits before it is saved. Turning that rounded number back into a string does not repair it. Test the full round trip through the actual transport and persistence layers, especially where spreadsheets may introduce scientific notation.

Keep decimals as independently evidenced metadata. A familiar symbol is not proof that a contract uses the expected scale, and matching symbols on different chains are not sufficient asset identities. If decimals are unknown, retain the atomic amount and the metadata gap rather than defaulting to eighteen. A raw quantity can remain useful even when a friendly display value cannot yet be justified.

Quantity is not valuation

The result is a token quantity, not a market price or fiat total. An exact amount can coexist with an unknown price. Do not convert missing price into zero or treat a unit conversion as proof of an asset’s economic value. See the historical balance guide, the decimals definition and the normalized record contract for the surrounding data model.