Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial![](https://ecs-static.teamtreehouse.com/assets/views/marketing/shared/community-banner-white-47072046c51352fe6a69f5e691ff5700b28bb11d45197d7bdf066d9ea3f72d0c.webp)
![Laura Hill](https://uploads.teamtreehouse.com/production/profile-photos/763562/micro_profile_pic.jpg)
Laura Hill
13,674 PointsChanges made in the browser's inspector aren't saved, they are just a place for testing. Correct?
I feel really dumb asking this question, like I must have missed something. I use dev tools to understand whats happening with the code, and how the browser is applying the rules. But, I know that any changes I might make are just for testing purposes, and I still have to go back to my text file and change it there, too. Right? Changes made in the browser aren't saved to the original doc, are they?
1 Answer
![Rick Gleitz](https://uploads.teamtreehouse.com/production/profile-photos/10566072/micro_highres_446837619.jpg)
Rick Gleitz
47,836 PointsYou are correct.
In the transcript for this video, Guil says 18 seconds in:
"And like the elements panel, changes you make aren't permanent. So they won't change the code in your CSS file."