16 SaaS websites using CSS-in-JS
SaaS websites built with CSS-in-JS (styled-components, Emotion, etc.). See how teams shipping on CSS-in-JS (styled-components, Emotion, etc.) design their landing pages, sections and overall visual style — useful if you're evaluating CSS-in-JS (styled-components, Emotion, etc.) for your own marketing site.
Sponsored by
(opens in new tab)
(opens in new tab)
About CSS-in-JS
CSS-in-JS libraries (styled-components, Emotion, and similar) let a team write component-scoped styles directly alongside the component's JavaScript rather than in a separate stylesheet, which was especially popular before Tailwind's utility-first approach became the more common default for new projects. A site using this approach today is more often one built during that earlier period — or one whose team specifically prefers colocating styles with logic per component — and it's functionally invisible to a visitor either way, since like Tailwind, it compiles down to ordinary CSS in the shipped page.
What makes a great one
- Consistent, component-scoped design that suggests a mature design system
From the blog
24 Product Landing Page Examples, Measured Fold to Footer
Twenty-four product landing pages read start to finish from our own screenshots — what's in the fold, where the logo strip actually sits, how the page closes, and how long each one really runs, in pixels.
25 SaaS Contact Us Page Examples, Counted Field by Field
Dropbox's contact form asks for eleven things. Warp's asks for one. We counted the fields, the routes and the published email addresses on 25 real SaaS contact pages — and not one of them promises a response time.
22 SaaS Affiliate Program Pages, and the Terms They Actually Publish
Semrush publishes a 120-day cookie window and a four-tier commission table. Typeform caps you at $500 per referral. Seven of these 22 pages publish no rate at all. A page-by-page read of what SaaS affiliate pages actually disclose.
Frequently asked
Can you tell from the outside that a site uses CSS-in-JS?
No — it's a development-time authoring choice that compiles to regular CSS in the final page, invisible to anyone but a developer inspecting the generated class names or bundle.