Title: content width
Last modified: January 27, 2017

---

# content width

 *  [Ufuk A.](https://wordpress.org/support/users/tindeks2/)
 * (@tindeks2)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/content-width-22/)
 * hi,
 * thank you for this free theme.
 * how can i incresae content width and dicrease sidebar width.
 * thank you in advance.,
    -  This topic was modified 9 years, 3 months ago by [Ufuk A.](https://wordpress.org/support/users/tindeks2/).

Viewing 1 replies (of 1 total)

 *  Theme Author [crskoglund](https://wordpress.org/support/users/crskoglund/)
 * (@crskoglund)
 * [9 years, 3 months ago](https://wordpress.org/support/topic/content-width-22/#post-8735399)
 * Hi [@tindeks2](https://wordpress.org/support/users/tindeks2/),
 * Thanks for the question. There is currently no way to do this via the customizer.
   I’ll look into including this feature in a future update.
 * In the meantime, you could accomplish this by adding the following to the bottom
   of the stylesheet:
 *     ```
       #secondary {
       max-width: 20% !important;
       }
   
       #primary {
       max-width: 75% !important;
       }
       ```
   
 * Replacing the 20% and 75% with your preferred widths for the sidebar and content
   respectively.

Viewing 1 replies (of 1 total)

The topic ‘content width’ is closed to new replies.

 * ![](https://i0.wp.com/themes.svn.wordpress.org/light-roast/2.1/screenshot.png)
 * Light Roast
 * [Support Threads](https://wordpress.org/support/theme/light-roast/)
 * [Active Topics](https://wordpress.org/support/theme/light-roast/active/)
 * [Unresolved Topics](https://wordpress.org/support/theme/light-roast/unresolved/)
 * [Reviews](https://wordpress.org/support/theme/light-roast/reviews/)

## Tags

 * [content width](https://wordpress.org/support/topic-tag/content-width/)

 * 1 reply
 * 2 participants
 * Last reply from: [crskoglund](https://wordpress.org/support/users/crskoglund/)
 * Last activity: [9 years, 3 months ago](https://wordpress.org/support/topic/content-width-22/#post-8735399)
 * Status: not resolved