Search tools

About ToolQuilt

ToolQuilt is a growing collection of free online tools for designers and developers, with a blog of practical guides, run as an independent project. No accounts, no sign up, nothing about you stored. This page explains how each tool works, so you can decide whether to trust its answers.

What ToolQuilt is

The name is the idea: a quilt of small tools, each one doing a single job well, stitched together in one place. The tools are grouped by the kind of work they help with, so far color and development, and new groups are added as new tools earn a place. Every tool follows the same rules: it is free, it needs no account, and it shows how it reached its answer.

How the color tools work

Everything is calculated on the server from first principles, not by a third party library, so the working can be inspected and corrected.

Contrast

The WCAG 2.2 ratio is (L1 + 0.05) / (L2 + 0.05), where L is relative luminance computed from linearized sRGB channels with the standard 0.2126 / 0.7152 / 0.0722 weights. Black on white gives exactly 21:1, which is the sanity check every implementation should pass.

The APCA score uses the published 0.1.9 constants: a 2.4 exponent transfer curve, separate coefficients for the two polarities, a soft black clamp at 0.022, and the low contrast clip at 0.1. Black text on white returns roughly Lc 106; white text on black returns roughly Lc −108. APCA is a candidate for WCAG 3 and is not yet a legal standard, so conform to WCAG 2.2 and use APCA as the second opinion that catches pairs which pass the ratio but still read badly.

Worked example: the same three pairs, scored

WCAG 2.2 · APCA 0.1.9
The quick brown fox
13.55:1 Lc 95.7 Passes AA · Body text
The quick brown fox
4.19:1 Lc 65.8 AA large only · Large text only
The quick brown fox
1.95:1 Lc 35.8 Fails AA · Decoration only
All three sit on the same background. The middle one is the trap: it looks deliberate, and it fails body text by a third of a point.

Color spaces

Conversions go through CIE XYZ under a D65 white point with the 2 degree standard observer. CIELAB and LCH follow the CIE definitions, including the linear segment below the 0.008856 threshold. OKLab and OKLCH use Björn Ottosson's published matrices. Round tripping any color through LAB or OKLCH and back returns the original hex.

CMYK is the simple arithmetic conversion with no color profile attached. It will get you into the right neighborhood and no further. Real print work needs an ICC profile for the specific press, paper and ink set.

Worked example: out to LAB and OKLCH, and back

Computed on this request
#C05746 → lab(50.06% 40.89 30.21) → #C05746 identical
#2F6F68 → lab(42.72% -22.26 -2.29) → #2F6F68 identical
#F2B134 → lab(76.42% 13.09 68.45) → #F2B134 identical
Every value returns the hex it started from. A conversion that cannot make this trip has dropped a coefficient somewhere.

Palettes and scales

Harmony rules set the hue relationships. Lightness and chroma are then spaced again in OKLCH, because HSL lightness does not match perceived lightness: yellow at 50% in HSL looks far brighter than blue at 50%. The 50 to 950 tonal scale holds hue, walks a fixed lightness ladder, and shapes chroma with a curve that peaks in the middle, which is what stops the lightest and darkest steps looking artificial.

Worked example: why HSL lightness is not lightness

Numbers are measured relative luminance

HSL, every swatch at 50% lightness spread 42 points

26% 52% 48% 24% 10% 18%

OKLCH, every swatch at the same perceptual lightness spread 4 points

22% 24% 25% 26% 23% 22%
The top row asks for one lightness and delivers 42 points of variation, and the yellow green is several times brighter than the violet. The bottom row asks the same question in OKLCH and lands within 4. That is the whole reason palettes here are spaced in OKLCH.

Color vision simulation

The protanopia, deuteranopia and tritanopia previews use the Machado, Oliveira and Fernandes (2009) matrices at full severity, applied in linear RGB. They are a reasonable model, not a medical instrument. Treat them as a prompt to add a second signal, such as a label, an icon or a pattern, wherever two swatches converge.

Worked example: one palette, four kinds of vision

Machado et al. (2009), full severity

As drawn: Standard color vision

Protanopia: No working red cones. Around 1 in 100 men.

Deuteranopia: No working green cones. Around 1 in 100 men.

Tritanopia: No working blue cones. Around 1 in 10,000 people.

→ #5AC1BA and #F4B7FF are ΔE₀₀ 39.5 apart normally and 13.0 apart under deuteranopia. That is the pair to give a second signal.

How the developer tools work

The developer tools do all of their work with JavaScript in your browser. What you type or paste into them is never sent to this server, and the site's security policy blocks its pages from sending data to any other site. Share links put the value after the # in the address, a part browsers keep to themselves.

JSON

The JSON formatter checks text against the JSON standard, RFC 8259, with its own parser rather than the browser's. That lets it point to the exact line and column of a mistake, keep every number exactly as written, including whole numbers too large for JavaScript to hold, and keep both copies of a key that appears twice. It has no share link, because JSON so often holds tokens and personal data.

Base64 and URL encoding

The Base64 tool has its own encoder and decoder rather than the browser's btoa and atob, which fail on anything outside Latin-1. Text is always converted through UTF-8, both the standard and the URL safe alphabets are read, and decoded data that is not text is recognized as the file it is. The URL tool encodes a single value, a whole URL or form data by their different rules, and points out broken percent sequences and text that was encoded twice.

JWTs, UUIDs and hashes

The JWT decoder reads tokens with the same Base64 and JSON code as those tools, and verifies HS, RS, PS, ES and EdDSA signatures with the browser's Web Crypto, using a secret, a PEM public key or a JWK. The UUID generator uses the browser's secure random numbers for version 4 and the RFC 9562 layout for time ordered version 7. The hash generator uses Web Crypto for the SHA family and its own implementation of MD5, and none of the three sends anything you enter to a server.

Cron expressions

The cron generator reads the standard five field format used by crontab, with lists, ranges, steps, month and weekday names and the @daily style shortcuts. It follows the rule cron itself uses for the two day fields: when both are restricted, a day that matches either one counts, unless one of them starts with *, in which case a day has to match both. Next run times are worked out by stepping through the calendar in your time zone or in UTC. They do not model the special handling a real cron service applies when daylight saving starts or ends, so for jobs between 1:00 and 3:00 on those nights, trust the server over the preview.

Unix timestamps

The timestamp converter uses the browser's own date functions. It decides the unit from the number of digits, reads microsecond and nanosecond values with exact whole number arithmetic so they are not rounded, and covers every date a browser can represent, which is roughly 270,000 years either side of 1970.

File permissions

The chmod calculator works on the twelve permission bits every Linux and Unix system uses: read, write and execute for the owner, the group and everyone else, plus setuid, setgid and the sticky bit. The number, the letters and the checkboxes are three views of the same value, and the letter form of the command is built from the same bits.

Privacy, in short

The full detail is in the privacy policy and the cookie policy. The summary:

  • No account system, so there is nothing to sign up for and no profile to leak.
  • Colors you enter travel in the URL query string so results are shareable. They are processed to build the page and are not written to any database.
  • The developer tools run entirely in your browser. Nothing you paste into them is sent to this server, and a security policy stops the pages from sending it anywhere else.
  • A single browser localStorage entry records whether you chose the light or dark theme. It never leaves your device.
  • No analytics script, no session recording, no fingerprinting.
  • No third party fonts, embeds or social widgets. Every asset is served from this domain.
  • Standard web server request logs may exist at the hosting layer, as they do for every website.

Standards this follows

  • WCAG 2.2, Success Criteria 1.4.3, 1.4.6 and 1.4.11.
  • APCA 0.1.9, as drafted for WCAG 3.
  • CSS Color Module Level 4 for parsing and output syntax.
  • CIE 15:2004 for XYZ, LAB and LCH.
  • RFC 8259 for JSON.
  • RFC 4648 for Base64 and its URL safe alphabet.
  • RFC 7519 and RFC 7515 for JSON Web Tokens and their signatures.
  • RFC 9562 for UUIDs, versions 4 and 7.
  • FIPS 180-4 for SHA, RFC 1321 for MD5 and RFC 2104 for HMAC.
  • RFC 3986 and the WHATWG URL Standard for percent encoding.
  • The POSIX crontab format, with cronie and Vixie cron's rule for the day fields.
  • POSIX file mode bits for chmod.
  • POSIX Unix time: seconds since the epoch, with no leap seconds.

Corrections

If a result here disagrees with a reference implementation, the result here is the one to doubt. There are a lot of places to drop a coefficient or misread a specification, and every tool on this site shows its inputs so a disagreement can be traced. Send corrections through the contact form; they are answered first.