# Why Bottles? ### Why a new application? Bottles was born in 2017 as a personal need. I needed a practical way to manage my wineprefixes. I hate the idea of using applications that install me a version of wine for each application and I decided to create this application, based on the concept of using one or more wine prefixes as a "container" for all my applications. In 2020 thanks to Valve, we have access to Proton. An optimized version of Wine for gaming. Thanks also to other projects like DXVK/VKD3D/Esync/Fsync/Shader compiler and others, we can run a large set of video games designed for Windows, on Linux. The idea of creating an environment-based wineprefix manager comes from the standardization of dependencies and parameters necessary to run a game. On the other hand, we have software (often not up to date) that require environments and configurations different from those used in gaming. Hence the idea of managing separate environments. ### Why not just POL or Lutris? Because they are similar but different applications. I want to create environments that contain more applications and games and where the wine version can be updated. I also want to be able to export my bottles allowing easy sharing, with or without applications. In POL/Lutris we have the concept of "with this version of wine and these changes it works". In Bottles the concept is "this is my wine bottle, I want to install this software". The goal with this version is also to integrate with the system in the best possible way. Being able to decide in a few bottles to run an .exe/.msi file and have control over it without having to open Bottles for each operation. Bottles is close to what wineprefix means, since v.2 it provides a simplified method to generate environment-based bottles and thanks to other tools it simplifies the management but nothing more. ### Main features There are some features that make Bottles unique: * a powerful, integrated and written from scratch [dependency manager](https://docs.usebottles.com/bottles/dependencies) based on a [community driven](https://docs.usebottles.com/contribute) and easy to expand repository * version control to easily [restore a bottle state](https://docs.usebottles.com/bottles/versioning) (goodbye disasters) * management based on pre-configured [environments](https://docs.usebottles.com/getting-started/environments) ready for **Gaming** or **Software**, with the most common dependencies pre-installed and an ad hoc configuration to immediately run a lot of software, you can also configure your environment from scratch * [full-sandbox](https://docs.usebottles.com/flatpak) (via Flatpak) * easy config or full [backup](https://docs.usebottles.com/bottles/backups) export and import, also cloning * [automatically detect installed programs](https://docs.usebottles.com/bottles/programs), no need to manually add to the programs list * 360° [customization](https://docs.usebottles.com/bottles/preferences) of the whole environment without having to go through winecfg * a fully integrated [installers manager](https://docs.usebottles.com/bottles/installers) also based on a [community driven](https://docs.usebottles.com/bottles/installers#repository-and-contributions) repository and much, much more. [Try Bottles](https://docs.usebottles.com/getting-started/installation) to discover all the features we have designed to make it easier for you to run Windows software on Linux! --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.usebottles.com/faq/why-bottles.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.