Android Studio Quail has picked up another important June update. Android Studio Quail 1 Patch 1 is now available on the stable channel, while Android Studio Quail 2 Canary 7 keeps the next preview branch moving for developers who want the newest tooling fixes before they reach a wider release.
If you simply want the current production release, Android Studio Quail 1 Patch 1 (2026.1.1) is now the right download. If you want early access to the next branch, Android Studio Quail 2 Canary 7 (2026.1.2) is the newest preview build available right now. Keeping both in one guide still makes sense, but the recommendation is now clearer than before.
In practical terms, this update is focused more on polish than a feature reset. Install Android Studio Quail 1 Patch 1 if you want the safest production-ready Android Studio release with the latest stable fixes. Keep Android Studio Quail 2 Canary 7 as a separate preview install if you want the latest Canary-side fixes, the newer AGP pairing, and the fastest look at where Android Studio is heading next.
Right now, the Quail release family is easiest to read as one stable patch release plus one active Canary branch:
Android Studio Quail 1 Patch 1
- Version: 2026.1.1 Patch 1
- Channel: Stable
- Release date: June 11, 2026
- Best for: normal development work, broader team rollout, and production use
- Not ideal for: developers who specifically want the newest Quail 2 preview changes before they settle further
Android Studio Quail 2 Canary 7
- Version: 2026.1.2
- Channel: Canary
- Release date: June 11, 2026
- Best for: early feature tracking, preview toolchain testing, and the latest Quail 2 fixes
- Not ideal for: developers who want the safest build for their main machine
If you are already on the stable channel, Quail 1 Patch 1 should now arrive through the normal Android Studio update path. If you are intentionally following the Canary channel, Quail 2 Canary 7 is the current branch to watch. For anyone coming from an older stable install, the safer move is still to keep the preview build separate so your main setup stays predictable.
Download Android Studio Quail
Here are the latest official Android Studio Quail download links for both the stable and Canary branches. Android Studio Quail 1 Patch 1 is now the default recommendation for most developers, while Quail 2 Canary 7 is the better fit if you want to stay on the next experimental track.
Download Android Studio Quail 1 Patch 1
| Platform | Android Studio package | Size |
|---|---|---|
| Windows (64-bit) | android-studio-quail1-patch1-windows.exe | 1.38 GB |
| Windows (64-bit ZIP) | android-studio-quail1-patch1-windows.zip | 1.38 GB |
| Mac (Intel) | android-studio-quail1-patch1-mac.dmg | 1.39 GB |
| Mac (Apple Silicon) | android-studio-quail1-patch1-mac_arm.dmg | 1.36 GB |
| Linux (64-bit) | android-studio-quail1-patch1-linux.tar.gz | 1.42 GB |
| ChromeOS | android-studio-quail1-patch1-cros.deb | 1.11 GB |
Download Android Studio Quail 2 Canary 7
| Platform | Android Studio package | Size |
|---|---|---|
| Windows (64-bit) | android-studio-quail2-canary7-windows.exe | 1.39 GB |
| Windows (64-bit ZIP) | android-studio-quail2-canary7-windows.zip | 1.39 GB |
| Mac (Intel) | android-studio-quail2-canary7-mac.dmg | 1.40 GB |
| Mac (Apple Silicon) | android-studio-quail2-canary7-mac_arm.dmg | 1.37 GB |
| Linux (64-bit) | android-studio-quail2-canary7-linux.tar.gz | 1.44 GB |
| ChromeOS | android-studio-quail2-canary7-cros.deb | 1.12 GB |
If you only want the normal installer on Windows, use the EXE package. The ZIP build is more useful if you prefer a portable-style setup or want more control over where the secondary install lives. For preview testing, that ZIP option is still one of the easier ways to keep Canary separate from your main stable environment.
Need help with setup? Follow our installation tutorial here:
What’s New in Android Studio Quail
The biggest Quail change now is that the stable branch already has its first patch. Android Studio Quail 1 Patch 1 keeps the current production release fresh with a targeted Running Devices fix, while Android Studio Quail 2 Canary 7 keeps the next branch moving for anyone who wants the earliest possible access to new IDE and AGP changes.
That split still makes the page easy to read. Quail 1 Patch 1 is the version to install if you want today’s recommended Android Studio build, while Quail 2 Canary 7 is the branch for developers who deliberately want the rougher but fresher preview experience.
Quail 1 Patch 1 is now the current stable release
Google has released Android Studio Quail 1 Patch 1 in the stable channel, which means Quail’s production branch has already moved past the first stable build. This is not a major feature drop, but it is the build most developers should choose if they are installing Quail fresh or updating their main development machine.
The listed fix targets Running Devices, specifically a laggy mouse interaction problem when using a mirrored hardware device after the Quail update. If you use Device Mirroring as part of your normal debug flow, Patch 1 is worth installing quickly rather than staying on the first Quail 1 stable release.
Google still lists Android Gradle Plugin versions 7.1 through 9.2 as compatible with Android Studio Quail 1, which keeps the stable release a clean upgrade target for a broad range of existing Android projects.
Quail 2 Canary 7 keeps the next branch moving
The preview side has not stopped just because Quail 1 is now stable. Android Studio Quail 2 Canary 7 is now available through Google’s preview download page, and it continues the next branch with another practical fix-focused refresh rather than a huge new public feature wave.
This release pairs with Android Gradle Plugin 9.3.0-alpha12 and covers a wider set of cleanup work than the previous Canary. Google lists fixes across Android Gradle Plugin, Code Editor, Gemini, Lint, Multiplatform, Project Structure, and Running Devices, including the same mirrored-device mouse lag issue addressed on the stable side.
That makes Canary 7 a more meaningful preview refresh than a simple package bump. It is still not the build most developers should use as their daily IDE, but it is the current Quail 2 build to test if you track the upcoming branch or validate projects against the newest preview AGP line.
AI-assisted crash analysis in App Quality Insights
One of the most useful Quail additions is still the AI integration inside App Quality Insights. Instead of only showing raw crash data, Android Studio can analyze the crash alongside your source code, explain likely causes, and help you move toward a fix with less back-and-forth between stack traces and affected classes.
That is the kind of feature that becomes much more relevant now that Quail 1 is stable. In preview form it was easy to treat as something interesting but optional. In the stable release, it becomes part of the normal IDE experience for teams that want faster debugging and a better first pass on crash triage.
If this works reliably in real projects, it is still one of the stronger reasons to move from an older Android Studio build to Quail rather than treating the upgrade as a routine version change.
Compose Preview Screenshot Testing
Google is also continuing to highlight Compose Preview Screenshot Testing as one of the practical Quail-era additions. The idea is simple: generate visual reports directly from Compose previews so UI regressions are easier to catch before they become harder-to-spot bugs in a full build or test cycle.
For teams already working heavily in Compose, this remains one of the most obviously useful Quail features. It fits modern Android workflows well because visual regressions are often subtle, repetitive to verify manually, and easy to miss until much later if the tooling does not help early enough.
LeakCanary integration inside Android Studio Profiler
The Quail cycle also adds tighter LeakCanary integration in Android Studio Profiler, which makes memory-leak investigation feel less detached from the rest of the IDE. Instead of bouncing between separate tools and mental contexts, the workflow becomes more unified inside the environment most Android developers are already using all day.
That matters most on larger apps where leak debugging can easily become a slow, fragmented job. Even without flashy marketing language around it, this is the kind of addition that can quietly save time over months of normal development work.
Recomposition state reads and UI debugging
Another Quail improvement worth keeping around is the extra visibility into Compose recomposition state reads. When UI performance or update behavior gets messy, the hardest part is often understanding why a recomposition happened and which state interaction triggered it.
Quail improves that story by making the inspection flow more explicit, and it pairs well with the broader push toward AI-assisted explanations in places where raw tooling data is useful but still too dense on its own. This is a grounded use of AI help, because it is tied directly to a debugging question developers already have.
Android Studio Quail Release History
This page will continue to be updated for every new Quail build so you can track the Quail 1 stable line and the moving Quail 2 Canary branch in one place.
Android Studio Quail 1 Release History
| Release | Version | Channel | Release date | Main highlights | Status |
|---|---|---|---|---|---|
| Quail 1 Patch 1 | 2026.1.1 | Stable | June 11, 2026 | Running Devices fix for laggy mouse interaction with mirrored hardware devices | Current stable build |
| Quail 1 | 2026.1.1 | Stable | June 2, 2026 | Quail moves into the production channel with stable compatibility and the full Quail feature set | Previous build |
| Quail 1 RC 2 | 2026.1.1 | Beta / RC | May 26, 2026 | Minor fixes and improvements; final pre-stable checkpoint | Previous build |
| Quail 1 RC 1 | 2026.1.1 | Beta / RC | May 19, 2026 | Minor fixes and improvements; Quail 1 moves to the Release Candidate stage | Previous build |
| Quail 1 Canary 5 | 2026.1.1.5 | Canary | May 14, 2026 | Compose Preview Screenshot Testing locale fix, L8 obfuscation mapping included in app mapping output | Previous build |
| Quail 1 Canary 4 | 2026.1.1.4 | Canary | May 7, 2026 | Android CLI Windows CreateProcess fix, KMP keepRules source set fix, API opt-in cleanup, AI inline code completion fix, Import/Sync fix | Previous build |
| Quail 1 Canary 3 | 2026.1.1.3 | Canary | April 30, 2026 | Android CLI config-cache fix, AGP Gradle 9.2.0 ClassNotFoundException fix, API opt-in cleanup, Google Login fix, Lint fix, Navigation Editor freeze fix | Previous build |
| Quail 1 Canary 2 | 2026.1.1.2 | Canary | April 24, 2026 | AGP native_libs_merge_blame_file support, Lint fixes, New Project Wizard config-cache default, UI Tools Otter 3 freeze fix | Previous build |
| Quail 1 Canary 1 | 2026.1.1.1 | Canary | April 16, 2026 | AQI AI crash analysis, Compose Preview Screenshot Testing, LeakCanary profiler integration, Material Symbols tooling, recomposition state reads | Previous build |
Android Studio Quail 2 Release History
| Release | Version | Channel | Release date | Main highlights | Status |
|---|---|---|---|---|---|
| Quail 2 Canary 7 | 2026.1.2 | Canary | June 11, 2026 | AGP 9.3.0-alpha12 pairing; fixes across AGP, Code Editor, Gemini, Lint, Multiplatform, Project Structure, and Running Devices | Current Quail 2 build |
| Quail 2 Canary 6 | 2026.1.2 | Canary | June 8, 2026 | AGP 9.3.0-alpha11 pairing; Device Mirroring Cyrillic keyboard input fix | Previous build |
| Quail 2 Canary 5 | 2026.1.2 | Canary | June 4, 2026 | AGP 9.3.0-alpha10 pairing; Gemini quota exhausted error no longer shown as internal error | Previous build |
| Quail 2 Canary 4 | 2026.1.2 | Canary | May 29, 2026 | AGP 9.3.0-alpha09 pairing; Android CLI / sdkmanager fixes; Gradle DSL parsing cleanup | Previous build |
| Quail 2 Canary 3 | 2026.1.2 | Canary | May 28, 2026 | AGP 9.3.0-alpha08 pairing; maintenance refresh before Canary 4 | Previous build |
| Quail 2 Canary 2 | 2026.1.2 | Canary | May 21, 2026 | Fast-follow Quail 2 update; paired with AGP 9.3.0-alpha07; Kotlin plugin code completion and indexing fix | Previous build |
| Quail 2 Canary 1 | 2026.1.2 | Canary | May 19, 2026 | Fresh Quail 2 branch opens; paired with AGP 9.3.0-alpha06; JavaDocGenerationTask workers fix; app termination fix | Previous build |
Android Studio Quail Release Channels Explained
Android Studio Quail now spans two very different use cases. Quail 1 Patch 1 is the stable production release, while Quail 2 Canary 7 is the newest preview build on the faster-moving branch. Once you separate those roles, the page becomes much easier to use.
Stable
Stable is the version most developers should use for regular work, and that is now Android Studio Quail 1 Patch 1. If you want the current production Android Studio release, this is the default branch to install.
Canary
Canary builds are the earliest public preview releases. They update quickly, bring in the newest experimental changes first, and are more likely to include bugs or workflow regressions. That is exactly where Quail 2 Canary 7 sits right now.
Beta and Release Candidate
Beta and Release Candidate stages are now part of Quail 1 history rather than the current recommendation. RC builds mattered during the transition to stable, but they are no longer the main branch to target unless you are looking back through the release progression.
Can You Install Android Studio Quail 2 Canary 7 Alongside Quail 1 Patch 1?
Yes, you can install Android Studio Quail 2 Canary 7 alongside Android Studio Quail 1 Patch 1 without replacing your current setup. Google supports side-by-side installs for preview builds, which is still the best way to test Canary without disrupting your main development environment.
That setup now makes even more sense. Keep Android Studio Quail 1 Patch 1 as your normal install, then use Quail 2 Canary 7 only when you want to try newer preview behavior, validate compatibility with the next toolchain, or check upcoming IDE changes ahead of time.
There are still a couple of practical things to keep in mind:
- Newer Android Studio builds can update some project configuration files in ways that may not play nicely with older versions.
- Android Studio installs typically share the same SDK location, so SDK updates can be visible across installs.
- If you are working on an important production project, keep Quail 1 as your primary environment and use Canary as a secondary test install.
For preview builds on Windows and Linux, Google still recommends extracting the archive into a uniquely named folder such as Android Studio Preview so it stays clearly separate from your main installation.
Android Studio Quail System Requirements
Android Studio Quail follows the same general installation requirements as current Android Studio releases. If you plan to use emulator-heavy workflows or newer AI-assisted features, it is still worth aiming above the minimums.
Windows
- 64-bit Windows 10 or newer
- 8 GB RAM minimum
- 16 GB RAM recommended if you use the emulator regularly
- 8 GB available storage minimum
- More storage recommended if you also install SDK platforms, emulator images, and command-line tools
macOS
- macOS 12 or newer
- Intel or Apple Silicon Mac
- 8 GB RAM minimum
- 16 GB RAM recommended for smoother emulator and large-project use
- 8 GB available storage minimum, with more recommended for full Android tooling
Linux
- 64-bit Linux distribution
- glibc 2.31 or newer
- 8 GB RAM minimum
- 16 GB RAM recommended if you use emulator and heavier IDE tooling
- 8 GB storage minimum, with more recommended for SDK packages and system images
ChromeOS
- ChromeOS device with Linux development support enabled
- 8 GB RAM recommended
- At least 10 GB available storage recommended
Android Studio Quail FAQs
Is Android Studio Quail stable?
Yes. Android Studio Quail 1 Patch 1 is now in the stable channel. The newer Quail 2 Canary 7 build is still an earlier preview branch for developers who want the next wave of changes.
What is the latest Android Studio Quail version?
Right now, the current production release is Android Studio Quail 1 Patch 1 (2026.1.1), while the newest preview branch is Android Studio Quail 2 Canary 7 (2026.1.2).
Should you use Android Studio Quail for production work?
Android Studio Quail 1 Patch 1 is now the normal production-ready branch. Quail 2 Canary 7 is better kept as a separate preview install for testing, experimentation, and early compatibility checks.
Does Android Studio Quail work with preview AGP builds?
Yes, but you should still match preview IDE builds with the corresponding preview Android Gradle Plugin line. Android Studio Quail 1 supports AGP 7.1 through 9.2, while Quail 2 Canary 7 is aligned with AGP 9.3.0-alpha12 on the faster preview branch.
Where can you download older Android Studio versions?
If you need an older release instead of Quail, use these Team Android guides:
- Android Studio Panda 4 Patch 1 (2025.3.4.7)
- Android Studio Giraffe (2022.3.1)
- Android Studio Flamingo (2022.2.1 Patch 2)
SHA-256 Checksums
Official SHA-256 values for every Quail 1 Patch 1 and Quail 2 Canary 7 download package are published on the Android Studio archive page. Use them to verify your downloads, especially after large IDE installs.
Quail 1 Patch 1 checksums
d738b85423c79f3320032907bf7a9684509cf119803d9705b15b93970473a58f— android-studio-quail1-patch1-windows.exe6f015829ca3c27333c12f32e888ab1e72543deb88d0af51bb6c4c842d65184bb— android-studio-quail1-patch1-windows.zip6f24e9d76456a3d5b5da42c6693bf2418e9ba4eb005c2b635ccee4e8684b4f67— android-studio-quail1-patch1-mac.dmg07145348f0b7bce6336eb362addd773093a84c40a4780f436beb6795a48b1270— android-studio-quail1-patch1-mac_arm.dmg2e29b43783b7ffd62f62389831fc3f260df1b8f673e5125caf588e75112e8eb5— android-studio-quail1-patch1-linux.tar.gzfb44da8ae02f62d7fa22447ad927aea9b6dc2b366121169ca71bb17942abce71— android-studio-quail1-patch1-cros.deb
Quail 2 Canary 7 checksums
ccea7731b852c00a07e683dcb51938b88c6d8ed3012e8fd54fc4ff7367716a4f— android-studio-quail2-canary7-windows.exea3d63fce5d08858c89849018c62e5f4c508e70766d4d1105bc0899d7b62a0400— android-studio-quail2-canary7-windows.zip5c6806c6e14d8568b749afd19d68bbe63e5c7ff870ff5ea9b2d91d952339e698— android-studio-quail2-canary7-mac.dmg92e4857f05603b8e23048afdef99246ef9d6851bae81f2e5f99dca97a08772e6— android-studio-quail2-canary7-mac_arm.dmg2c7b337c0b4ce592cd6d3646d22b1bf9a516deec29fb36affe28074f81c37843— android-studio-quail2-canary7-linux.tar.gzc8d9e216c1090cec4cf3397b318138a538eb043348d163bd96778c527a61c8e0— android-studio-quail2-canary7-cros.deb
Android Studio Quail has now entered the more useful part of its lifecycle. Android Studio Quail 1 Patch 1 is ready for normal development work, while Quail 2 Canary 7 keeps the next preview track active for developers who want to stay ahead of the main release line. The reasons to care about Quail are still the same: better crash analysis, stronger Compose validation, improved debugging visibility, and a more capable modern Android IDE overall.
This page will be updated every time Google releases a new Quail build, so if you want one place to track Quail downloads, branch progression, and the ongoing Canary line after stable, keep checking back here.
For official background and ongoing changes, Google is currently splitting Quail information across the Android Studio Quail 1 Patch 1 announcement, the Android Studio Quail 1 release notes and downloads, the Quail 1 closed issues page, the Android Studio preview download page, the Quail 2 closed issues page, the preview install guide, and the Android Studio release channels documentation.
