---
title: "Comment by info on \"CSS Comparison for Responsive Design: From Basics to Modern Frameworks\" | Hashnode"
description: "Great comparison, especially the discussion around px , em , and rem . I’ve found that the biggest challenge when moving from fixed px values to scalable rem un"
url: "https://hashnode.com/posts/css-comparison-for-responsive-design-from-basics-to-modern-frameworks/66ea706753d4f45ae585531a/comment/6a965e225e038d5f5aa6ecad"
---

[Discussion](https://hashnode.com/posts/css-comparison-for-responsive-design-from-basics-to-modern-frameworks/66ea706753d4f45ae585531a)

Comment [CSS Comparison for Responsive Design: From Basics to Modern Frameworks](https://hashnode.com/posts/css-comparison-for-responsive-design-from-basics-to-modern-frameworks/66ea706753d4f45ae585531a)

[info](https://hashnode.com/@utilityforweb)

[Sep 1](https://hashnode.com/posts/css-comparison-for-responsive-design-from-basics-to-modern-frameworks/66ea706753d4f45ae585531a/comment/6a965e225e038d5f5aa6ecad)

Great comparison, especially the discussion around `px`, `em`, and `rem`. I’ve found that the biggest challenge when moving from fixed `px` values to scalable `rem` units is doing the conversions consistently across a stylesheet. A px to rem converter can make that process much quicker, and having a rem to px converter is useful when you need to work backward or verify existing values. I’ve been using this [https://www.utilityforweb.com/px-to-rem/](https://www.utilityforweb.com/px-to-rem/) tool for quick two-way conversions while working on responsive layouts.
