简体中文
English
Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Amino?
Amino is a browser extension that lets you apply your own CSS to any website, with those changes persisting across visits. Its stated purpose is customizing sites, including building your own themes and skins, using a compact live CSS editor rather than a full development environment.
What that means in practice
- Live editing: You write CSS and see the result on the page as you work, which suits quick visual tweaking over structured stylesheet authoring.
- Persistence: Styles are saved, so a site looks the way you styled it on return visits instead of resetting each session.
- Any site: The pitch is site-agnostic customization, so the same tool covers a site with no built-in theming and a site whose official theme options are limited.
Who gets the most out of it
The natural audience is someone comfortable reading a page's markup and writing selectors, but who doesn't want to fork a userscript or maintain a separate stylesheet pipeline. Typical uses: toning down a distracting interface, enlarging text on a site you read daily, hiding elements you never use, or giving a familiar site a personal color scheme. If you don't know CSS at all, an extension that ships ready-made themes will get you further faster.
Trade-offs to weigh
Custom CSS is fragile by nature. When a site redesigns its markup, selectors that depended on old class names or structure stop matching, and your styles quietly break until you fix them. Site updates can also override or conflict with what you inject. Treat your customizations as personal patches that need occasional maintenance, not a one-time setup. A live editor makes the fix easier, but it doesn't remove the upkeep.
Next step: Pick one site you visit often and one small annoyance, such as an oversized sticky header or low-contrast sidebar text. Write a single rule for it, confirm the change sticks after a reload, and use that as your test of whether this workflow fits how you browse.
How do I install Amino as a browser extension?
Amino is a browser extension that lets you apply custom CSS to any website and keep those changes persistent, so installing it means adding it through your browser's extension system rather than downloading a standalone app.
General installation steps
- Open your browser's official extension gallery (Chrome Web Store, Firefox Add-ons, or the equivalent for your browser).
- Search for "Amino" and confirm the listing matches the developer and description you expect.
- Select Add to Chrome / Add to Firefox and approve the permissions prompt.
- Pin the extension to your toolbar so you can open the CSS editor from any page.
- Open a site, launch Amino, and write a rule such as
body { background: #111; }to test that changes apply and persist after a reload.
What to check before installing
- Browser compatibility: confirm your browser is supported, since extension APIs differ between Chromium-based browsers and Firefox.
- Permissions: a CSS editor typically needs to read and modify page content on the sites you visit. That is expected for this kind of tool, but review the prompt rather than clicking through it.
- Persistence behavior: the value of Amino is that styles survive page reloads and navigation. Test this on one site before building out a full theme.
A practical first use
Pick a site you visit daily and change one small thing — a font stack, a background color, or hiding a distracting sidebar element. That single test tells you whether the editor's selector targeting and save behavior fit how you work. If you want to compare approaches, Firefox Add-ons and the Chrome Web Store both host CSS-injection extensions with different persistence and sync models, which is worth checking if cross-device syncing matters to you.
How do I write CSS in Amino to customize a website?
Amino is a browser extension built around a live CSS editor: you open a site, write CSS, and the changes apply as you type and persist on that site afterward. The intended workflow is write-and-see, not edit-deploy-refresh.
The basic loop
- Install the Amino extension in your browser (Amino).
- Navigate to the site you want to restyle.
- Open the Amino editor from the extension toolbar.
- Write CSS targeting that site's elements. The page updates live, so you can iterate on selectors and values immediately.
- Save or confirm, so the stylesheet persists and reloads with the page.
What to write
You're writing ordinary CSS, so the practical work is choosing selectors and overriding existing rules. A typical small customization:
/* Hide a distracting sidebar */
aside.promo-rail { display: none; }
/* Widen the reading column */
main article { max-width: 72ch; margin: 0 auto; }
/* Darken the background */
body { background: #14161a; color: #e8e8e8; }
Because you're layering on top of someone else's stylesheet, specificity and !important matter more than they would in your own project. Start with the simplest selector that works, and only escalate specificity when a rule is being overridden.
A realistic first project
Suppose you read long documentation on one site and find the text column too narrow and the font too small. Open Amino on that page, inspect the article container to get its class, then set a wider max-width, a larger font-size, and a comfortable line-height. Check a second page of the same site, because a selector that works on one template may not match another. Save once the result holds across the pages you actually use.
Trade-offs to keep in mind
- Per-site persistence is the point. Your CSS is tied to the site, so it follows you across visits without touching the site itself.
- You don't control the markup. When the site changes its classes or structure, your selectors can break and need updating.
- Overrides can be fragile. Heavy use of
!importantfixes today's conflict and creates tomorrow's confusion; comment your rules so future-you knows why they exist. - It's presentation only. Amino changes how a site looks in your browser, not what it serves to anyone else.
Starter tip: keep your rules grouped and commented by purpose (layout, typography, hiding elements), so a broken site is quick to diagnose. For broader browser-side customization beyond CSS, extensions such as Firefox Add-ons and Chrome Web Store are where you'd compare alternatives.
Will my Amino CSS changes persist after I close the browser?
Yes. Amino is built around persisting CSS changes, so a rule you add to a site stays applied the next time you load that site and after you quit and reopen the browser. That persistence is the main difference between Amino and the temporary style tweaks you can make in browser developer tools.
What persistence means in practice
- Your edits are stored as per-site custom CSS, not as a one-off change to a loaded page.
- Reopening the browser, restarting the machine, or navigating away and back should reapply the CSS automatically.
- Because the styles live in the extension, they generally follow your browser profile rather than a single tab session.
The trade-offs to plan for
| Situation | Expected behaviour | Practical implication |
|---|---|---|
| Normal browsing in the same browser profile | Styles reappear on each visit | Safe for long-term themes and skins |
| Private/incognito window | Extensions are often disabled or isolated | Expect your styles not to apply there |
| Different browser or device | Separate extension install and separate storage | You would need to recreate or export the CSS |
| Site redesign or class-name change | Selectors may stop matching | Plan to revisit your rules occasionally |
A concrete example
Suppose you hide a distracting sidebar on a news site and enlarge the body text. After closing and reopening the browser, that site should load with the sidebar hidden and the larger text, without you redoing anything. If a site later ships a redesign, the sidebar may reappear because the old selector no longer matches — that is a selector problem, not a persistence failure.
Next step
Before investing time in a large theme, test persistence deliberately: make one obvious change, fully quit the browser, relaunch it and reload the page. If it survives, your setup is behaving as intended. If you rely on these styles across machines, keep a plain-text copy of your CSS so you can paste it into a fresh install. For browser-level customisation beyond CSS, Firefox Add-ons and Chrome Web Store are where extension listings live.
Can I create and share website themes or skins with Amino?
Amino is built for exactly this: applying custom CSS to websites you already use, and keeping those changes so they persist across visits. Whether that adds up to a shareable "theme" depends on where the CSS lives.
What the product supports
Amino is a browser extension with a live CSS editor. You open a site, write CSS against it, and the extension stores the result, so your custom look returns the next time you load the page. The natural uses are cosmetic and personal: hiding elements you find distracting, restyling a site's typography or colors to reduce eye strain, or making a cluttered interface quieter for daily reading.
The sharing question
The page evidence describes customization and persistence, not a theme gallery, import/export, or a publishing mechanism. So treat "shareable skin" as two separate things:
| Goal | What it requires |
|---|---|
| Your own custom look on a site | CSS written in the editor and saved locally |
| Someone else seeing the same look | A way to hand over the CSS text, plus the same extension installed |
In practice, sharing usually means copying your CSS out of the editor and sending it to another person, who pastes it into their own Amino setup. That works fine for a friend or a small team, but it is manual: there is no evidence of one-click theme links, community browsing, or versioned theme packages.
Practical test before you invest time
Write a short stylesheet for one site you visit daily, save it, close the browser, and reopen the page. If it comes back, persistence works as advertised for your setup. Then send that same CSS to one other person and have them apply it. If the paste-and-apply step is easy enough, informal sharing is viable for you; if you need a distribution channel, this is the wrong tool.
Where Amino fits versus alternatives
Amino is a good match if you want per-site CSS tweaks without maintaining a userscript or a full styling extension configuration, and if your audience is small and technical enough to copy CSS. It is a poor match if you want to publish a theme that strangers install with one click, or if you need to style pages that block extension injection.
For broader styling that many people already use and share configurations for, Stylebot and UserStyles.world are established places where user-created styles are distributed, and Violentmonkey handles userscripts that can include styling. Those are different workflows with their own learning curves, so pick based on whether distribution matters more than a quick local edit.
Is Amino free to use?
The page itself does not display a pricing statement, so there is no confirmed answer from Amino's own site about whether it is free. Treat cost as something to verify directly in the browser's extension store listing before installing.
What to check for a definitive answer
- Open the extension's store page (Chrome Web Store, Firefox Add-ons, or Edge Add-ons) and look at the "Price" or "Free" label.
- Check whether the listing mentions in-app purchases, subscriptions, or a paid tier.
- Look for a "Pro" or "Plus" plan on the developer's site, which would indicate a free core with paid extras.
Practical scenario
If you only need to tweak a site's fonts, colors, or spacing for personal use, a free tier is usually enough. If you want syncing across devices, shared theme libraries, or team features, expect those to sit behind a paid plan.
Decision criterion
Install it, apply a small CSS change, and reload the page. If the change persists without a prompt to pay, you are on the free experience. If a paywall appears at save or sync, you have your answer immediately.
Cloudflare
Netlify
Google Workspace
User reviews (0)