Color, in your control.
Utilities from the forge corner.
What Forge is for.
Forge is for front-end and web work. The four main tools cover the handoff from design to code: turn one brand color into a full scale, build a gradient, convert pixel values to rem, and test a regular expression before it goes into your code. The utilities further down handle the formats you paste around all day: JWTs, JSON, Base64, URLs, CSV, QR codes, SVG, HTML, and CSS.
Everything in Forge runs in your browser. Regex patterns and sample text stay in the page. Tokens you paste into the JWT decoder are decoded locally, and the decoder does not verify signatures, so a token that decodes cleanly is not proof it is genuine. The color and gradient tools write their main settings into the page address, so a link reopens the same palette or starting gradient.
Which tool to open
Questions people ask.
Is the color scale the same as Tailwind’s?
It uses the same step names, 50 to 950, so it drops straight into a Tailwind theme. The colors are not Tailwind’s. Each step sets a fixed lightness at your color’s hue, from 97% at 50 down to 8% at 950, so your exact hex is usually not one of the swatches. Pick the closest step as your brand step.
Should I use px or rem in CSS?
Use rem for font sizes and most spacing. It scales with the reader’s browser font-size setting, and px ignores that setting. Keep px for things that shouldn’t scale, like 1px borders. At the default 16px root, 24px is 1.5rem.
Which regex flavor does the tester use?
JavaScript, through your browser’s own RegExp engine, so patterns behave the way they will in JavaScript, TypeScript, or Node. Features from PCRE, Python, or .NET, such as possessive quantifiers and atomic groups, either throw an error or mean something else.
Does the JWT decoder check the signature?
No. It decodes the header and payload so you can read the claims and the expiry time. Anyone can build a token that decodes cleanly. Verify the signature on your server with the signing key before you trust a token.