brunodev85/winlator

Android application for running Windows applications with Wine and Box86/Box64

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 3 minutes ago
Added to GitGenius on September 3rd, 2026
Created on July 26th, 2023
Open Issues & Pull Requests: 403 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 1,721
Total Stargazers: 18,939 (+0)
Total Subscribers: 353 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

Winlator is an Android application that enables running Windows x86_64 applications on Android devices through Wine and Box86/Box64 translation layers.

The tool addresses the challenge of executing Windows software on ARM-based Android devices by combining Wine, which provides Windows API compatibility, with Box86/Box64, which translates x86_64 instructions to ARM. Users install the application, wait for its initialization process to complete, and can then launch Windows programs directly from their Android device. The approach leverages existing compatibility layers rather than building emulation from scratch, allowing a broader range of Windows software to run on mobile hardware.

Winlator suits developers and users who need to run Windows applications on Android phones or tablets, particularly those working with older games or legacy software. The tool includes configuration options for different use cases: performance presets for Box64, environment variable settings for compatibility with specific game engines like Unity, and per-application shortcut settings for individual optimization. Users experiencing issues with .NET Framework applications can install Wine Mono, while those running older games may need to adjust graphics extension settings or enable fullscreen scaling. The project builds on established open-source components including Wine, Mesa graphics libraries, DXVK, and VKD3D rather than reimplementing these systems.

Development activity shows consistent engagement with user-reported issues and practical troubleshooting guidance. The README provides detailed tips for resolving common problems such as audio crackling, performance bottlenecks, and compatibility issues with specific game engines, indicating active maintenance focused on real-world usage scenarios. The project maintains clear attribution to upstream dependencies and acknowledges contributors to the broader ecosystem it depends on.