Chrome-Stats extension
CSS Scan
The fastest and easiest way to check, copy and edit CSS.
Total ratings for CSS Scan
3.78
(Rating count:
68)
User reviews summary
These summaries are automatically generated weekly using AI based on recent user reviews.
Chrome Web Store does not verify user reviews, so some user reviews may be inaccurate,
spammy, or outdated.
Pros
- Speeds up work
- Useful for frontend developers
- Great for inspecting and manipulating CSS
- Easy to use
Cons
- Requires payment for full functionality
- Issues with copied unnecessary CSS
- Inconsistencies in displaying CSS
Most mentioned
- Speeds up work
- Requires payment for full functionality
- Useful for frontend developers
Upgrade to see all 57 reviews
Recent reviews for CSS Scan
Recent rating average:
3.50
All time rating average:
3.78
Upgrade to see all 57 reviews
Rating filters
5 star
4 star
3 star
2 star
1 star
| Date | Author | Rating | Lang | Comment |
|---|---|---|---|---|
| 2024-05-02 |  |
|
en | Simply worst |
| 2024-04-18 |  |
|
en | Pure s#it. It asks for license and you have to pay $67 to use it. |
| 2024-01-19 |  |
|
en | works really well. CodePen feature is awesome and speeds up work a lot! |
| 2024-01-06 |  |
|
pt | Ferramenta muito boa e prática! Facilita até o dia a dia de desenvolvedores backend! |
| 2024-01-06 |  |
|
en | Great extension overall, works perfectly on all websites I tested it in, and is pretty fast doing so! Specially useful for frontend developers, but a great tool for any kind of engineer or curious people really. Totally recommend it whether you've just started learning CSS/frontend development or you're an experienced engineer. |
| 2023-08-25 |  |
|
Amazing, only 2 problems: 1) When you inspect element and activate the mobile view on Chrome CSS Scan doesn't work very well... 2) Why have an "inherited-style"? I don't understand the logic. It would be so much simpler to keep the name of the original class. | |
| 2023-08-09 |  |
|
Sellout | |
| 2023-06-01 |  |
|
Does what it says, and seems to be designed with care. A couple things which limit the value for me: 1. it's opinionated when displaying certain CSS; padding, for example: I have a site where I've set the padding for several elements using four specific declarations ie padding-left, padding-right, padding-top, padding-bottom. The extension squashes this into "padding: 17px 12px 17px 16px" Why is it doing this? The browser itself (inspector) doesn't squash CSS like this, and the extension, running in the browser, has the same amount of screen available as the browser, meaning space is not an extreme issue that would require the extension to arbitrarily refactor the code, making it harder to review for those who are looking for what they actually wrote 2. To really be a replacement for inspector, there needs to be a viewport width indicator stuck to the top of the page. I didn't realize this is the single feature that makes inspector so efficient, especially with regard to CSS (resizing the screen with precision to work on responsiveness). Related to that, this tool has also made me aware that prototyping and testing / checking responsiveness (how styles change at different screen sizes), is like 90% of the CSS work I use inspector for. Which brings me back to the value of displaying the viewport width when the extension is running One thing that really sold me on this was the ability to quickly capture other people's CSS. I may feel more strongly about this purchase after trying that out. Very impressed with the design quality of this extension so far overall, visually and functionally. | |
| 2023-04-05 |  |
|
A great plugin. It works near perfect. Rarely have they failed to detect on some special hovers. It would be even better if it was added to devtools. | |
| 2023-03-15 |  |
|
Works well. |
Upgrade to see all 57 reviews