> For the complete documentation index, see [llms.txt](https://docs.droptopfour.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.droptopfour.com/getting-started/installation.md). # Installation How to install Droptop Four ## Requirements * **Windows 10** or above * **Rainmeter** v4.5.7 or above ([download here](https://www.rainmeter.net/)) ## Installation Download the `Droptop Basic Version.rmskin` file from below: {% embed url="" %} After downloading the file, launch the .rmskin install file and select "Install". Follow the setup guide. {% hint style="warning" %} You must have started Rainmeter at least once before installing Droptop! {% endhint %} ## Installing the Supporter Version You can support the developers of Droptop Four by purchasing the Supporter version. As a Supporter, you will receive: * 18 additional themes not available in the Basic version * 6 additional fully-customizable dropdown folders * 5 additional slots for Community Apps * 293 additional home button icons (full-color and black & white) You can purchase the Supporter version through [Gumroad](https://gumroad.com/l/droptop) with a suggested purchase price of $6. Droptop operates on a pay-what-you-want model. --- # 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.droptopfour.com/getting-started/installation.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.