The problem
Getting the exact colour from a live page is a daily task for designers and front-end developers. A client says match the green on their site, a developer needs the brand blue from a reference page, a designer wants to check a shade used in a banner.
Screenshot-based pickers are often slightly off. They sample pixels from an image, so scaling, compression and colour profiles can shift the value, and a near-match is not good enough when brand colours have to be exact. Switching tools to convert a value between formats adds more steps, and people lose the colours they picked a minute ago.
The need was simple: get the true colour, in the format you need, and keep it close at hand.
These small errors add up. A colour that is a few values off may pass unnoticed in one place and then show up as a visible mismatch when two elements sit side by side.
What we built
Color Picker Doctor reads the colour from the page itself rather than guessing from a picture of it.
- HEX, RGB and HSL outputs, so the same colour can go to CSS, a design tool or a style guide
- Colour history, so earlier picks are not lost during a session
- Copy to clipboard in one click, which removes the retyping step where mistakes creep in
The point of the history and copy features is the workflow around the pick. Choosing a colour is only half the job; the other half is getting it into the file where it is needed, and any friction there makes people fall back on eyeballing.
The extension is built with Chrome APIs on Manifest V3. We took it through the whole publishing process, including the store listing and privacy policy. If you want a small, focused tool like this, see our Chrome extension development service.
Reading the colour from the page also means the value matches what the site actually uses, which is what you want when the goal is to reproduce a brand colour or document a palette for a client.
The result
Color Picker Doctor is live on the Chrome Web Store, built for workflows where the exact colour matters. It is one of Medkon's own products, so the build, the privacy policy and the store submission were all done in-house.
For clients, it shows what a small, single-purpose extension looks like when it is finished properly.
If your team has a similar daily micro-task in the browser, a focused extension is often a smaller and quicker project than people expect, and we can tell you on a call whether it is worth building.
Frequently asked questions
How do you build and publish a Chrome extension?
We scope the single job the extension should do, build it on Manifest V3 with the Chrome APIs it needs, test it across the browsers your users run, then prepare the store listing, screenshots and privacy policy and submit it. We handle the submission for you.
What is Manifest V3 and does it matter?
Manifest V3 is the current extension platform required by Chrome. It changes how background logic and permissions work. Building on it from day one avoids a forced rewrite later and keeps the extension eligible for the store.
How long does Chrome Web Store review take?
It varies, and it is controlled by Google rather than by us. Clear permissions, an honest description and a privacy policy help it go smoothly. We handle the submission and any follow-up questions from the reviewers.
How much does a custom Chrome extension cost?
Pricing is project-based. A fixed quote follows a free discovery call, once we know what the extension needs to do. A fix or plugin-sized job is usually 1-2 weeks, and a full store, app or platform is 4-8 weeks.