Bottles on SteamOS

Scope

Bottles manages separate Wine environments for Windows applications and games. It is best suited to controlled per-application prefixes, not as a replacement for every store launcher.

Trust boundary

Each bottle contains Windows executables, registry state, dependencies, runner configuration, and user data. Flatpak limits host access only according to granted permissions; exposing all of home or removable storage expands that boundary.

Supported installation

Install the official com.usebottles.bottles Flatpak through Discover. Create one bottle with the appropriate application/game environment, choose an explicit storage location, and install only from a verified vendor source.

Verification

Record Bottles version, Flatpak permissions, bottle environment, runner, dependencies, executable hash/source, and storage path. Launch inside Bottles before adding a Steam shortcut; then verify the shortcut separately.

Update

Update the Flatpak through Discover. Back up a working bottle before changing its runner or dependency set. Do not apply dependency installers to every bottle without a demonstrated requirement.

Uninstall

Remove Steam shortcuts and inventory bottle-local saves first. Uninstall the application separately from bottle data. Do not use data-deleting Flatpak options until backups and cloud state are verified.

Rollback

Restore the prior runner/dependency configuration or import a known-good bottle backup. If only a shortcut fails, recreate it while preserving the bottle and game installation.

Recommended use

Use Bottles for isolated Windows applications, custom prefixes, or manual installers that benefit from explicit runner and dependency control. Use Heroic or Lutris when their store/script integration is the primary requirement.

Frequently asked questions

Is a Bottle a security sandbox?
Is a Bottle a security sandbox?
Not by itself. It isolates Wine configuration, while Flatpak permissions, exposed files, network access, and Windows executables still define the security boundary.
Can I delete a Bottle after exporting a Steam shortcut?
Can I delete a Bottle after exporting a Steam shortcut?
No. The shortcut still depends on the application, runner, and bottle. Back up and remove the shortcut before deleting the bottle.

Sources

Version history

  • 2026-07-15: Phase 6 Flatpak, prefix isolation, permission, backup, and rollback review.