HexColor Pro is an independent, free color toolkit for web designers and developers. It offers 13 browser-based tools for picking colors, generating CSS gradients and palettes, checking WCAG contrast, and converting between HEX, RGB, HSL, HSV, and CMYK — plus a written guide and a blog on color theory and accessibility.
Every tool runs entirely in your browser. Nothing is uploaded: colors you enter are processed by JavaScript on your device, and no account is required to use any feature. The pages are static HTML served from a CDN, so they load fast and work the same on any modern browser.
HexColor Pro is free and supported by advertising. Ads never gate a tool and never change a computed result — the color math is plain JavaScript you can inspect in the page source.
HexColor Pro is built and maintained by Yao Xiangqian, an independent developer (github.com/yxq1337). It started as a set of internal utility pages for everyday design work — checking a contrast pair, converting a hex value, building a quick gradient — and was published so other people could use them without a signup or a paywall.
Every tool is written and tested by the same person who writes the articles, so a claim on a blog page and the behavior of the tool on the adjacent page come from the same implementation. Questions, corrections, and tool requests go to the contact page.
Yao Xiangqian is an independent developer who builds small, self-contained browser tools. Every tool on this site — the WCAG contrast math, the HEX/RGB/HSL/HSV/CMYK conversions, the mixing and ramp generation — is plain JavaScript written for that page, with no framework and no build step. The articles come from the same person, so a claim about how a ratio is computed can be checked against the code that computes it, one click away.
The work here is front-end — semantic HTML, plain CSS, and client-side JavaScript — and behind it sit ten years of design-system work: component libraries and color systems where a token that fails contrast is a bug, not a taste difference.
The tool pages and articles are written by the maintainer. Where a claim depends on a standard, it cites the primary source — accessibility thresholds follow the W3C Web Content Accessibility Guidelines (WCAG) 2.2, published 5 October 2023, rather than secondary summaries. Articles show a publication date, and are revised when a cited standard or browser behavior changes.
If you spot an error, say which page and what is wrong; corrections are made on the page itself rather than in a reply, so the next reader sees the fix.
You are welcome to quote or cite these pages with a link back. Machine-readable descriptions for AI agents are published at llms.txt and llms-full.txt.