> For the complete documentation index, see [llms.txt](https://help.vectary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.vectary.com/documentation/project-settings/loading-screen.md). # Loading screen ## Overview The Loading Screen feature enables the customization of the project's loading interface. This feature allows changing every aspect of the loading screen, including the background, preloader, and defining whether the project loads automatically or upon button interaction.

## Background

* **Color**: set the color for the loading screen * **Use cover image**: when activated, the project's cover image is used as the background * **Blur**: enables blurring of the cover image ## Preloader Upload a custom preloader in PNG, JPG, SVG, GIF, or Lottie format.

## Play button By default, projects load automatically. Disabling the **Autoplay** option will require end-users to initiate loading by pressing a play button. * The play button can be customized using PNG, JPG, SVG, GIF, or Lottie formats.

--- # 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://help.vectary.com/documentation/project-settings/loading-screen.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.