> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/customization/brand-winpe-background.md).
# Brand WinPE Background
Many organizations customize deployments with their own logos and backgrounds. DeployR supports this in WinPE by adding an image named `winpe.jpg` to the **Extras** content item.
### Create your Source Folder Structure
Create the following folder structure in the content item: `Content Root\Windows\System32\winpe.jpg`. In this example, the content root is the "ExtraFiles" folder.
Note: anything you add to these folders is copied into WinPE with the same folder structure. For example, \Windows\System32\CMTrace.exe in the image above is copied into WinPE, where it is located at X:\Windows\System32\CMTrace.exe.
### Create the Content Item
After selecting **Open after creation**, click **Save**. The new content item opens, and you can click **New Version**.
Optionally, add a description, then click **Save**. Click **Choose File**, then browse to the root of the source folder you want to upload, and click **Upload**.
When prompted to upload the files, click **Upload**.
A list of the files to upload is displayed. Click **Upload All**.
The content item is now created and can be set in your Boot Image.
Once you have set the Content Item in the "Extra files" content item location in the boot image, click "Generate Image" and wait for it to complete.
You will now have your custom branded background image in WinPE.
---
# 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://documentation.2pintsoftware.com/deployr/customization/brand-winpe-background.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.
