Site customization
Customize a published GitBook site.
Customizing your site lets you control the branding, presentation and extra features of your site's public content. You can access your site's customization settings from the settings tab from your docs site's overview page.

General
Control how your content looks in the General tab. The available options are:
Layout: manage navigation options for your content
Configure: manage the interface
What counts as ‘Advanced customization’?
Every GitBook user can take advantage of basic customization options on their docs site. Pro or Enterprise plan users can also use advanced customization features to further tweak their docs to match their brand.
Advanced customization options include:
Custom logo – Add a logo that replaces the emoji and title at the top of your docs site.
Custom font – Change the font of your docs to one of the built-in options.
Footer – Add a custom logo, copyright text and navigation to a footer at the bottom of your documentation.
Bold, Contrast and Custom themes – Customize the primary color of your docs, as well as setting the background color for your header and the links within it.
Ask GitBook AI – Let your users ask anything about your product from the Search menu. GitBook AI will scan your documentation and provide a plain English answer in seconds.
What cannot be customized?
The options above provide lots of ways for you to customize your space, but there are a few things that you won’t be able to customize, regardless of your chosen plan.
It’s not possible to customize the layout of the elements on the page. (However, it is possible to hide certain elements on a page-by-page basis)
There’s no way to insert custom code, such as CSS, HTML, JS, etc., directly into one or more documentation pages. If you’re looking to integrate a third party service, take a look at the docs for our integrations platform. We already integrate with a number of popular tools, and offer rich embeds for many more.
It’s not possible to remove the small "Powered by GitBook" link that appears in published documentation.
Last updated
Was this helpful?