Title: Simple CSS vs custom.css Last modified: August 22, 2016 --- # Simple CSS vs custom.css * [delidoodle](https://wordpress.org/support/users/delidoodle/) * (@delidoodle) * [11 years, 2 months ago](https://wordpress.org/support/topic/simple-css-vs-customcss/) * I am worried that the customizations I am placing in a custom.css folder in a Canvas child theme will disappear when the child theme gets updated. I assume that the Simple Custom CSS plugin is not simply creating a custom.css folder and placing it in the child theme folder. * [https://wordpress.org/plugins/simple-custom-css/](https://wordpress.org/plugins/simple-custom-css/) Viewing 3 replies - 1 through 3 (of 3 total) * Plugin Author [John Regan](https://wordpress.org/support/users/johnregan3/) * (@johnregan3) * [11 years, 2 months ago](https://wordpress.org/support/topic/simple-css-vs-customcss/#post-5907102) * You are correct, it is not adding a new custom.css file or folder anywhere on your site. * It saves your CSS into the WordPress options table in your database, and when it is called in your it adds the CSS to your page via a custom link. Because this is saved in the database, it will not be overwritten by a theme update. * If I can add any more information to help you out, please let me know! * John * Thread Starter [delidoodle](https://wordpress.org/support/users/delidoodle/) * (@delidoodle) * [11 years, 2 months ago](https://wordpress.org/support/topic/simple-css-vs-customcss/#post-5907109) * I have used your plugin on sites where I am only making a few modifications. Works quite well. When making multiple modifications I prefer working with a text editor using a child.css file in the child theme directory. Does updating a purchased child theme like Canvas/Uno leave the custom.css alone? I have searched wordpress.org without success. Thanks. * Plugin Author [John Regan](https://wordpress.org/support/users/johnregan3/) * (@johnregan3) * [11 years, 2 months ago](https://wordpress.org/support/topic/simple-css-vs-customcss/#post-5907111) * Hi delidoodle, * I’m glad you’re enjoying the plugin! * I don’t know the specifics of updating paid child themes, but it’s safest to assume that the custom.css will be overwritten. As you probably know, the WP method of updating themes does delete then replace the theme with the latest version, and I’d assume that updating a paid theme would do the same. * Personally, I’m looking forward to the day when we can create “grandchild” themes to customize child themes. 😀 * I hope this helps! * John Viewing 3 replies - 1 through 3 (of 3 total) The topic ‘Simple CSS vs custom.css’ is closed to new replies. * ![](https://ps.w.org/simple-custom-css/assets/icon-256x256.jpg?rev=1819543) * [Simple Custom CSS Plugin](https://wordpress.org/plugins/simple-custom-css/) * [Support Threads](https://wordpress.org/support/plugin/simple-custom-css/) * [Active Topics](https://wordpress.org/support/plugin/simple-custom-css/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/simple-custom-css/unresolved/) * [Reviews](https://wordpress.org/support/plugin/simple-custom-css/reviews/) ## Tags * [child theme](https://wordpress.org/support/topic-tag/child-theme/) * 3 replies * 2 participants * Last reply from: [John Regan](https://wordpress.org/support/users/johnregan3/) * Last activity: [11 years, 2 months ago](https://wordpress.org/support/topic/simple-css-vs-customcss/#post-5907111) * Status: not resolved