Colour is a decision, not a decoration
Most tool sites treat colour as a lookup table — paste a hex code, get an RGB triplet, move on. EdiToolkit is built for the people who have to defend those numbers in a design review. When you pull a swatch from a client's photograph, that colour becomes a brand token, a button state, a hover shade, and eventually a line in a stylesheet that thousands of visitors will stare at. Our Image Color Picker exists so you can sample the exact pixel you mean — the highlight on the product, not the shadow beside it — and copy it in HEX, RGB and HSL without squinting at a native eyedropper that snaps to the wrong point. Zoom in, hover, read the value, paste it into your design token. That small act of precision is the difference between a palette that feels intentional and one that feels borrowed.
The Color Palette Extractor and Dominant Color Finder take the same idea further. Drop in a hero photograph, a moodboard, or a competitor's landing page screenshot, and you get five to ten dominant colours ranked by how much of the frame they actually occupy — not a random spread of pretty tints. Designers use this to reverse-engineer a mood, to check whether a photograph will sit comfortably beside an existing brand palette, or to build a scheme that already lives inside the imagery rather than fighting it. Because everything runs in your browser, you can throw unreleased campaign artwork at it without worrying that the file left your machine.
From swatch to system: HEX, RGB, HSL and CMYK
A single colour rarely stays in one format. You picked it in HEX from a mockup, your CSS wants RGB with an alpha channel, your motion designer thinks in HSL because rotating a hue is how they build gradients, and the print vendor only speaks CMYK. The HEX to RGB and HEX RGB HSL Converter tools are here so that translation never becomes a source of drift. Convert once, see a live preview swatch, and copy whichever notation the next tool in your pipeline expects. The HSL view in particular is worth leaning on: it separates hue from saturation and lightness, which means you can build a full tonal ramp — a 100-through-900 scale for a design system — by holding hue steady and stepping lightness, instead of guessing hex codes by eye.
Working in HSL also makes accessibility easier to reason about before you ever open the contrast checker. Lightness is roughly the lever that governs whether text on a background will pass, so nudging that single value gives you a fast, intuitive first pass. When you commit those colours into variables, keep the format consistent across the codebase; mixing raw hex in one component and rgba() in another is how palettes quietly diverge over a year of shipping.
Accessibility is where good colour proves itself
A palette that looks stunning in a Dribbble shot can still fail real people. The Contrast Ratio Checker tests any text-and-background pair against WCAG AA and AAA thresholds — 4.5:1 for normal body text, 3:1 for large headings — and shows the result live as you adjust the colours. Use it the moment you assign a colour to type, not as a compliance chore at the end. A grey that reads as "soft and modern" at 3.2:1 is unreadable for a huge slice of your audience on a sunny day or a cheap laptop panel, and fixing it early costs a nudge of lightness rather than a redesign.
The Color Blindness Simulator answers the question that contrast alone can't: does the design still make sense when hue disappears? Roughly one in twelve men has some form of colour vision deficiency, so previewing your interface through protanopia, deuteranopia and tritanopia filters catches the classic failures — red/green status pills that become identical, charts that rely on hue alone to separate series, error states signalled only by a colour change. Pair it with the Image Alt Text Generator, which walks you through writing genuinely descriptive alt text with a live character count, and you cover both the visual and the semantic sides of an accessible image. Together these turn "we should be accessible" into a checklist you can actually run before launch.
The metadata you can't see is the part that matters
Every photo you export carries a hidden layer: EXIF and IPTC metadata recording the camera, the timestamp, the software, and — most dangerously — GPS coordinates of exactly where the shot was taken. The Image Metadata Viewer lets you inspect all of it, and the Image GPS Location Viewer plots any embedded coordinates on a map so you can see at a glance whether a file is about to reveal a home address or an unannounced office. This isn't paranoia; newsrooms strip metadata as standard practice for precisely this reason, and a single un-scrubbed upload has ended people's anonymity.
The EXIF Metadata Remover closes the loop by stripping that data locally, before the image ever goes near a server, so you can publish clean files without an anxious round-trip through some unknown uploader. Round out the workflow with the Image SEO Filename Optimizer, which turns IMG_4821.jpg into a readable, keyword-aware slug that helps both search engines and screen-reader users. Whether you're a UI designer defending a palette, a front-end developer wiring colour tokens into a system, or an accessibility auditor signing off a release, these tools share one philosophy: colour and images are craft, and craft deserves instruments that respect your attention. Bookmark the ones you reach for, and let the fiddly parts — the conversions, the checks, the scrubbing — happen in seconds so you can spend your time on the decisions that actually need a human.