JSON to SQL Insert
Turn an array of JSON records into INSERT statements, with an optional CREATE TABLE.
Convert a hexadecimal string to Base64, standard or URL-safe.
Spaces, colons, hyphens, underscores, line breaks and a 0x prefix are all stripped, so you can paste straight from a hex dump or a certificate fingerprint.
The Hex to Base64 converter reads hex however it was written — spaced, colon-separated, 0x-prefixed or continuous — and outputs standard or URL-safe Base64 for the same bytes.
Hex and Base64 are two ways of writing the same bytes. Hex is easier to read a byte at a time, which is why hashes, keys and packet dumps use it; Base64 is a third shorter, which is why payloads and headers use it. Converting between them is a routine step and a fiddly one by hand.
The reader is deliberately forgiving about how the hex is written. Spaces, colons, hyphens, underscores, line breaks and a 0x prefix are all stripped before conversion, so you can paste straight from a hex dump, a certificate fingerprint, a MAC address or an OpenSSL output without cleaning it up first. Output can be standard Base64 or the URL-safe variant that JWTs and query parameters need.
Spaces, colons, hyphens, underscores, line breaks and a 0x prefix are stripped, so you can paste straight from a dump or a fingerprint.
The hyphen-and-underscore alphabet JWTs and query parameters need, with padding optional.
An odd number of hex digits means a byte is incomplete, and it is reported rather than silently guessed at.
How many bytes were read, which is the quickest way to spot a truncated paste.
The conversion is local, so key and certificate material is not uploaded anywhere.
Spaces, colons, hyphens and a 0x prefix are all fine — they are stripped automatically.
Standard Base64, or the URL-safe alphabet with hyphen and underscore.
The stat row confirms how many bytes were read, which catches a truncated paste.
Take the result to your clipboard.
Because each byte is exactly two hex digits. An odd count means at least one digit is missing, and guessing which end it belongs to would silently corrupt the data.
Yes. Colon-separated fingerprints, space-separated hex dumps and continuous strings are all accepted — the separators are stripped before conversion.
A variant that replaces plus with hyphen and slash with underscore, because those two characters have meaning inside a URL. JWT tokens use it, and padding is usually omitted.
No. The conversion runs in your browser, so keys and certificate material never leave your machine.
What people who use the Hex to Base64 think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the Hex to Base64. It takes half a minute and no account.
Write the first reviewTurn an array of JSON records into INSERT statements, with an optional CREATE TABLE.
Generate an MD5 hash of any text, with a straight answer about when not to.
Validate an IBAN's length, country and mod-97 checksum, and generate test ones.
Encode and decode Base32, including the Crockford and hex variants.
Convert between bytes, KiB, MB, GB and bits, in both systems.
Check an email address against the rules that actually matter, and see why.
Your browser, engine, platform, languages and what it supports.
Convert a duration between seconds, ISO 8601, clock time and words.