The fastest way to reach us is email: hello@nxtolerance.com.

What to write about

Codec bugs (highest priority). If valid base64 is rejected — or invalid input decodes silently to wrong bytes — tell us the smallest input that reproduces it. If the data is sensitive, truncate or redact the middle of the string; codec bugs live in the alphabet, padding and wrapping, not in your secrets. Please include the error message and the character position the tool reported.

Confusing error messages. If a message sent you looking in the wrong place, that counts as a bug too. “It said invalid character but the real problem was a data: prefix” is exactly the kind of report that improves the messages for everyone.

Feature requests. Reasonable asks we’ve heard: base32/base58 variants, wrap-at-76 output for MIME-style strings, batch decode, URL parameters to pre-fill the input. If you keep reaching for something the tool doesn’t do, describe the workflow — where the base64 came from and what you needed to do with it is more useful than a bare feature name.

Everything else. Broken pages, accessibility issues, partnership requests, corrections to the base64url, data URL or bugs articles. Please include the URL of the page you’re writing about.

What to expect

We’re a small team and read every message. Bug reports with a reproduction case are usually answered within a few days; general feedback may take longer. No ticket system, no automated replies — a person reads and answers your email.