A plain-text version of this site for AI assistants is at https://contengi.com/llms.txt, with the full product documentation in one file at https://contengi.com/llms-full.txt. Every page is also available as markdown by adding .md to its URL.

Free tool / Design system generator

Turn any website into a design system.

Paste a URL. We load the page in a real browser and read every element on it: the palette with roles, fonts and type scale, spacing, buttons, the logo and brand assets, the imagery, icons, motion and layout the site really uses. Then you get a consistency score, with the fix for every problem, and exports for CSS, Tailwind, JSON and Markdown.

Plain code, no AI model Same site, same system, every time Nothing you scan is stored

What comes out the other side

Everything a designer would write down after a day with the site open, from the colour of the buttons to how the pictures are cropped, in about ten seconds, and the same every time.

Colour with roles

Canvas, surfaces, line, text, body, muted, accent and on-accent, each chosen from where the colour does its job on the page. Plus contrast for every pair that matters.

canvasaccentcontrastgradients

Type

The fonts that set the text, where they load from, and the real size, weight, line height and tracking of each heading level and the body.

familiesscaleweightsline height

Logo, brand and imagery

The logo on light and dark, favicon, share image and web manifest. Then the pictures themselves: a preview of each, whether it is photographic or sits on a plain background, its shape, corners, format, weight, alt text, and the colours inside it.

logoshare imagephoto stylealt text

Icons and motion

Outline or solid icons, stroke weight, sizes and the likely icon set. Transition speeds, every easing curve drawn as a graph, and whether the site respects reduced motion.

strokeicon seteasingdurations

Space, shape and layout

The spacing steps and whether they sit on a grid, corner radii, shadows, content width, breakpoints, section padding, grid columns, and how the header behaves.

spacing gridradiishadowssections

Components

Primary, secondary and ghost buttons and form fields, grouped by how they look, with fill, text, border, radius and padding.

buttonsinputsvariants

Tokens and stack

The CSS variables the site defines and how often its CSS reads them, plus whether it is built on Tailwind, Bootstrap, WordPress, Webflow, or Framer.

custom propertiesframeworksCSS weight

Consistency score

Thirty-one checks across seven areas: too many greys, text that fails contrast, mixed icon strokes, six button styles where three would do, pictures without alt text, motion that ignores reduced-motion settings. Each with the fix.

greyscontrasticonsimagerymotion

How it decides what’s what

A stylesheet lists every colour the author could use. A page shows the ones it does use, and how much. So we don’t parse the CSS file and guess. We load the page, scroll it like a reader, and ask the browser for the computed style of every visible element.

Each colour gets its role from the job it does. The accent is the colour on the buttons and links. The canvas is the colour behind the most page.

The trade-off is honest. Code can read what a site does and can’t read what it means, so treat the roles as a first draft from a careful assistant, then adjust.

Canvas

The colour that covers the most page height. We sample the left edge of the page every 200px from top to bottom and take the most common.

Surface and line

The next backgrounds by area that sit clearly apart from the canvas, and the most used border colour.

Text, body, muted

Headline colour from the H1, body colour from real paragraphs, muted from the most common quieter text. Each must be readable on the canvas.

Accent

The colour doing jobs: button fills, links, colour tokens named primary or accent, the theme colour. Heavy ink colours are ruled out.

Type and sizes

The most common style of each element, weighted by how many characters it sets, so one oversized hero line can’t outvote the body text.

Imagery

We keep the pictures the page really loaded and measure their pixels. One colour carrying the frame reads as a plain background, a handful of flat colours as a graphic, and many colours with nothing dominant as photographic.

Motion and icons

Every transition is read before the page settles. Anything over 1.2 seconds is ambient and ignored. Icons are the small inline SVGs, grouped by how they are drawn.

FAQ

Common questions

Does it use AI?

No. It loads the page in a headless browser, reads the computed style of every visible element, and tallies the results. Every role and score is plain code you could follow by hand. Scan the same site tomorrow and, if the site has not changed, you get the same design system.

Why read the page and not just the CSS file?

A stylesheet tells you what the author could use. A page tells you what it does use, and how much. Themes and frameworks ship hundreds of colours and sizes that never appear on screen. Reading computed styles skips those, and it works the same for Tailwind, CSS-in-JS, and minified bundles.

How are the colour roles decided?

From usage. Canvas is the colour covering the most page height. The accent is the colour doing the most jobs: button fills, links, tokens named primary or accent. The section above lists every rule. They are inferences, so look them over before you rely on them.

How does it read the imagery without AI?

It keeps the pictures the page really loaded and draws each onto a small canvas to count colours. One colour carrying most of the frame reads as a plain background (product shots, interface, illustration). A few flat colours throughout reads as a graphic. Many colours with nothing dominant reads as photographic. It can’t tell a product photo from an illustration on the same backdrop, and the page says so. Previews are made during the scan, so your browser never loads the site’s images itself.

What can’t it see?

It reads the first load of one page at desktop width, in the default theme. Dark mode, hover and focus states, other pages, video, and anything behind a login are not scanned. A design system also holds things code can’t read: intent, voice, and when not to use something.

What is the consistency score?

Thirty-one checks across colour, type, space and shape, components, imagery, motion, and foundations. Each passes, warns, or fails, with contrast and alt text counting extra. It measures how consistent the design is. How good it looks is a separate question, and big sites with many sub-brands naturally drift more.

Can I use the output in Contengi?

Yes. The Markdown export follows the shape of Contengi’s own corporate identity section, so you can paste it into the design system settings and the visuals Contengi makes will follow it. The CSS, Tailwind and JSON exports work anywhere.

Is the page I scan stored?

No. We load it, send the raw tallies to your browser, and your browser builds the design system. The only thing we log is your IP address and the time, so one person can’t run hundreds of scans an hour.

Why did it fail on my site?

Some firewalls turn away every automated visitor, and pages behind a login or a bot check show our scanner nothing to read. If the site loads in a normal browser but not here, that is usually the reason.

A design system your content tools actually follow.

Contengi keeps your colours, type and logo next to your knowledge base, so the one-pagers, social graphics, slides and blog covers it makes already look like you.

Also free: the helpful content checker, the AI bot view, the AI slop cleaner, and the LLM visibility check.