What Stylus is

Stylus installs community themes from online style repositories or .user.css URLs and lets you write and edit your own stylesheets per site. The project started after the original Stylish extension was sold to a web analytics company, and it is built on Stylish's earlier code.

Feature coverage

  • Install styles from repositories or .user.css URLs
  • Built-in editor with optional code validators
  • Automatic style updates and full backup

What stands out

  • Open source with a public GitHub project
  • Developer declares no data collection
  • Updated in September 2026

Tradeoffs to know

  • All-sites access is required to inject styles
  • Writing your own styles assumes CSS knowledge
  • Site redesigns can break installed styles

Permissions and privacy

Page access

The listing explains that Chrome offers no way to change a page's appearance without full access to that page, and Stylus asks for it globally because many people apply site-wide themes. It says that access is used to add style elements, not to read your data. Chrome's site-access settings can narrow it to the sites you actually restyle.

Data notes

The listing declares no data collection, and the project's privacy policy says Stylus collects nothing. Styles are stored in the extension, and the backup feature exports your style database to a file you control. Installing a style from an online repository fetches it from that site, and automatic updates check those sources again.

Pricing

Free and open source. Pricing and plan limits change more often than store metadata, so use the linked developer page as the final check before subscribing.

Alternatives

AlternativeTampermonkeyAlternativeDark Reader

Sources

We used the official Chrome Web Store listing and first-party developer material. Public metrics can change after the fact-check date.

  1. Chrome Web Store listing

    Rating, rating count, public users, version, update date, and publisher disclosures verified 2026-10-12.

  2. Stylus product documentation

    First-party product, feature, support, or project documentation used for workflow context.

  3. Extension Reviewer methodology

    How public claims, permissions, evidence, and tradeoffs are reviewed.

View in Chrome Web Store Developer site
Read nextVisBugRead nextColorZilla

More in Developer tools

See the developer tools guide