Humanizer

Human-friendly formatting for Elixir. One flat module of pure functions that turn raw values into the strings you actually show to people — file sizes, durations, relative time, large numbers, ordinals and list enumerations.

English-only, zero configuration, no global state. Replaces a handful of single-purpose dependencies (filesize, humanize_time, ad-hoc helpers) with one.

Installation

Add humanizer to your mix.exs:

def deps do
  [
    {:humanizer, "~> 0.1.0"}
  ]
end

Documentation is on HexDocs.

Quick start

Humanizer.bytes(2_456_789)
# => "2.5 MB"
Humanizer.bytes(2_456_789, system: :binary)
# => "2.3 MiB"

Humanizer.duration(3725)
# => "1 hour, 2 minutes"
Humanizer.duration(45, format: :short)
# => "45s"

Humanizer.relative_time(~U[2026-05-13 10:00:00Z], ~U[2026-05-15 10:00:00Z])
# => "2 days ago"

Humanizer.number(1_234_567)
# => "1.2M"

Humanizer.ordinal(23)
# => "23rd"

Humanizer.list_join(["Alice", "Bob", "Charlie"])
# => "Alice, Bob and Charlie"

Every function takes its options as a keyword list — there is no Application env and nothing to configure globally.

API

Numbers use one consistent rule: round-half-away-from-zero with a single fractional digit by default (override with :precision). Output is never in scientific notation, for any input up to 10 ** 15.

Localization

English only in v0.1. This is deliberate. Real localization means pluralization, gender, grammatical cases and locale-specific decimal separators — a single bytes/1 under locales is a project of its own.

If you need serious internationalization, use ex_cldr and ex_cldr_numbers. Localization may arrive in a later version as an optional layer, but it is out of scope here.

Comparison

Humanizer is not "better than everything". It replaces four or five small dependencies with one, if English output is enough for you.

License

MIT. See LICENSE.