Extension Permission Monitor
Developer Tools
Audit extension permissions locally — no data leaves your browser. See what your extensions can access and safely disable unused tools.
Developer Tools
Extract website color palettes, generate design tokens, check WCAG contrast, and export colors for frontend projects.

Color palette — detected colors with hex values, role labels, and copy controls
Color Scheme Extractor helps developers and designers inspect the color system used on the current website.
Open the extension on a page, click Analyze, and review the detected palette, semantic color roles, CSS variables, contrast results, and export options. Analysis runs locally in your browser and only starts when you choose to analyze the active tab.
Built for
Web designers, frontend developers, and brand managers who need to inspect or replicate a site's color system.
Problem solved
Designers and developers waste time manually identifying brand colors and contrast ratios from sites they want to reference or audit.
Extract colors from backgrounds, text, links, buttons, borders, SVG elements, and CSS custom properties
Group similar shades to make palettes easier to review
Identify semantic roles: primary, secondary, accent, background, surface, text, link, border, error, warning, success, and info
Detect available CSS custom properties from the page
Review WCAG contrast ratios for detected color combinations
Copy colors as HEX, RGB, HSL, or CSS variable references
Export as CSS variables, SCSS variables, LESS variables, JSON tokens, Figma Tokens JSON, and SVG palette files
Save recent analyses and favourite colors locally
Light, dark, or system theme in the popup
Inspect individual elements on the page to view their detected colors
Visit a website you want to inspect
Open Color Scheme Extractor from the Chrome toolbar
Click Analyze
Copy or export the colors and tokens you need
Color Scheme Extractor runs analysis locally in your browser. It does not send website content, extracted colors, browsing history, settings, or favorites to an external server. Settings, recent analyses, and favorites are stored locally on your device through Chrome storage.
Why this extension requests each permission.
activeTab
Used to access the current tab when the user opens the extension and chooses to analyze the page.
scripting
Used to run the color scanner and optional element inspector on the active tab. Scripts run only after the user clicks Analyze or enables the inspector.
storage
Used to save settings, recent analyses, and favorite colors locally on the user's device.
tabs
Used to read the current tab URL, title, and favicon so the popup can display page context and save it with local analysis history.
host permissions (<all_urls>)
Required so the scanner can run on websites selected by the user. Analysis is user-initiated and does not run automatically.
Developer Tools
Audit extension permissions locally — no data leaves your browser. See what your extensions can access and safely disable unused tools.
Fityra Blog
Technical deep dives, build-in-public updates, and lessons learned shipping Chrome extensions and indie products.