> For the complete documentation index, see [llms.txt](https://wiki.libreelec.tv/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.libreelec.tv/how-to/change-bootscreen.md). # Change Bootsplash LibreELEC displays the project logo as a background "splash" screen during boot. This can be changed to your own image by placing `oemsplash.png` in the boot partition. Copy your splash image to the Downloads folder, then SSH into your LibreELEC box. Next we must remount the boot partition in read-write mode so we can make changes: ``` mount -o remount,rw /flash ``` Copy your splash image to the boot partition, renaming it to `oemsplash.png` ``` cp /storage/downloads/yoursplash.png /flash/oemsplash.png ``` Remount the boot partition in read-only mode: ``` mount -o remount,ro /flash ``` On reboot you should see the new bootsplash. ### Splash Image Requirements Splash images must be a 32-bit png files with 1920 x 1080, 1280 x 720, or 1024 x 768 pixel dimensions. Images will be upscaled to the active display resolution, so it is best to use the largest resolution (but not 4k, as most boot firmware does not support 4k output). Most OS image editors do not support 32-bit png export, so we recommend the excellent and open-source [GIMP](https://www.gimp.org) editor for making boot splashes. --- # 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://wiki.libreelec.tv/how-to/change-bootscreen.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.