> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-create-a-capsule-collection/capsule-header-dimensions.md). # Capsule header dimensions See the correct dimensions of a Capsule header to fit in the header area and maintain high quality. Headers are used in Capsules to indicate which collection the Capsule belongs to. When you create a new collection, you must upload the header and select the capsule color. Capsules have a hexagonal format and the header is located in the upper part of this hexagon. Therefore, the image size of the header must be larger to fill the hexagonal format, but the logo must be smaller to be fully displayed, as shown in the following figure:
Representation of a Capsule symbol to illustrate the position of the header in the hexagon.
## Header dimensions The header file must be in `.jpg` or `.png` format and have the following dimensions: * **Header width:** 180px * **Header height:** 40px * **Logo width:** 90px * **Logo height:** 24px The logo must be placed centrally in the image. This way you get a padding of 8px on top and bottom and a padding of 45px on both sides.
Header dimensions, including width, height, and paddings.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.digibee.com/documentation/development-cycle/build-overview/capsulas/how-to-use-capsules/how-to-create-a-capsule-collection/capsule-header-dimensions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.