The problem
Many websites have no dark mode, and long reading sessions at night are hard on the eyes. A bright white page in a dark room is uncomfortable, and operating system settings do not reach sites that never added a dark theme.
Simply inverting colours is a blunt answer. It can turn images into negatives and make some pages unreadable, and a single fixed level of darkness does not suit everyone. Some people want a soft dim; others want near-black.
We wanted a way to get a comfortable page on any site, with enough control that each person can set it to taste.
Eye comfort is also personal. Someone reading in a dark room wants something different from someone working beside a window, which is why a single switch is not enough.
What we built
Dark Mode Pro applies a dark theme to any site, whether or not the site supports one.
- Customisable darkness level, so it can be tuned to the room and the reader
- Blue-light filter for evening use
- Night-shift mode for late sessions
- Works on sites without native dark mode, which is where it is most useful
The technique behind this kind of tool is CSS injection: the extension adds styling to the page after it loads and adjusts it according to the settings you choose. The hard part is not applying a dark background but handling the variety of real pages, so the controls matter as much as the theme itself.
It is built on Chrome APIs and Manifest V3, with the listing, privacy policy and store submission handled by us. For similar work, see our Chrome extension development service.
Because it works on any site, a person sets their preferences once instead of hunting for dark-mode settings site by site, and sites without any such setting are covered too.
The result
Dark Mode Pro is live on the Chrome Web Store and makes long sessions easier on the eyes. It works across sites rather than one at a time.
As with our other extensions, it is a Medkon product that we took from idea to published listing ourselves.
It shows our approach to extension work: pick a real daily annoyance, give people control over it, and handle the store process so the result reaches users.
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.
Why do extensions ask for permissions?
Chrome only lets an extension touch pages or features it has declared permission for. A good extension asks for the minimum it needs and explains why. We keep permissions narrow and say what they are for in the listing.
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.