World’s largest virtual agentic engineering & quality conference
Galaxy Z Fold8 and Z Fold8 Ultra are now live on TestMu AI Real Device Cloud on Android 17, before retail. Test your site and app before users hold the device.

Vaishali Vatsayan
Author
Srinivasan Sekar
Reviewer
Last Updated on: July 30, 2026
Samsung announced the Galaxy Z Fold8 and the Galaxy Z Fold8 Ultra at Galaxy Unpacked on July 22, 2026. Both are already live on TestMu AI Real Device Cloud, running Android 17, and no customer is holding one yet.
General availability starts August 7, 2026, per Samsung's US launch announcement. That gap is the opportunity. You can test your website and your app on the real hardware now, and fix what breaks before your users hold the device in their hands.
Samsung introduced three foldables together, and the Galaxy Z Fold8 Ultra is the first Ultra model in the Z series. The two Folds are not a large and small version of the same device. They unfold into different shapes, which is the detail that matters most for testing. Specifications below come from Samsung's Galaxy Z Fold8 announcement.
Divide width by height and the two devices separate. The Fold8 main display resolves to 0.755, taller than it is wide. The Fold8 Ultra resolves to 1.110, wider than it is tall.
| Screen | Galaxy Z Fold8 | Galaxy Z Fold8 Ultra |
|---|---|---|
| Main resolution | 1,848 x 2,448 | 2,504 x 2,256 |
| Main aspect ratio | 0.755, portrait | 1.110, landscape |
| Cover resolution | 1,248 x 1,972 | 1,080 x 2,520 |
| Cover aspect ratio | 0.633 | 0.429 |
That is roughly a 1.47 times difference in aspect ratio between two devices that share a name, a chipset, and an operating system. A layout tuned on one of them will not automatically hold on the other, and neither device is in a single customer's hands yet to tell you about it.
The Samsung foldable inventory now spans four generations of the Galaxy Z Fold line. Availability differs by model, and the difference matters if you plan to automate.
| Device | Android version | Live session | Automation |
|---|---|---|---|
| Galaxy Z Fold8 Ultra | 17 | Available | Available |
| Galaxy Z Fold8 | 17 | Available | Available |
| Galaxy Z Fold7 | 16 | Available | Available |
| Galaxy Z Fold4 | 13 | Available | Not listed |

Because the four Folds sit on three different Android versions, the line doubles as an OS matrix inside a single form factor. A bug that reproduces on all three is almost always your layout code, while one that appears only on Android 17 usually points at a platform behavior change you can handle centrally.
Two caveats worth stating plainly. The Galaxy Z Fold4 stays available for manual work but drops off the automation list, so treat it as an exploratory device. The Galaxy Z Flip line is not part of this release either, so if your device matrix includes a Flip, keep testing it where you test it today. The current list of real devices shows exactly what is bookable.
A foldable gives your site two viewports on one device, and the Fold8 pair gives you four across the two models. Every one of them can be opened in a browser session today.
If you want a refresher on structuring breakpoints for a range this wide, our guide to responsive testing covers the approach.
Note: Test your site and app on a real Galaxy Z Fold8 before the devices reach customers. Both new foldables are live on Android 17 with no hardware to buy. Try for free
App behavior on a foldable depends on a physical hinge, which is exactly what an emulator cannot give you. These are the checks worth running first on the real device cloud.
The configuration-change case produces the most bug reports, because it is invisible on a conventional handset. Our comparison of emulators, simulators, and real devices covers where each option stops being useful.
For automation, the Fold8 models are addressable through standard Appium capabilities. Real device execution is opt-in, so isRealMobile has to be set explicitly or the session runs against a virtual device instead:
const capabilities = {
"lt:options": {
"username": "YOUR_USERNAME",
"accessKey": "YOUR_ACCESS_KEY",
"platformName": "Android",
"deviceName": "Galaxy Z Fold8",
"platformVersion": "17",
"isRealMobile": true,
"app": "lt://APP_ID",
"build": "Fold8 Layout Regression",
"name": "Unfolded layout on the main display"
}
};
// Mobile hub endpoint for real device sessions
const hubUrl = "https://mobile-hub.lambdatest.com/wd/hub";Swap deviceName to Galaxy Z Fold8 Ultra to run the same suite against the second form factor, which is the comparison that exposes the aspect-ratio failures. The Appium testing documentation covers app upload and the full capability set, and app automation handles parallel execution once you are running both devices.
Samsung put two foldables with opposite unfolded orientations into the same generation, and both are on TestMu AI Real Device Cloud on Android 17 while the shelves are still empty. Retail units arrive on August 7.
Run your layout suite against the Galaxy Z Fold8, repeat it on the Galaxy Z Fold8 Ultra, and diff the two result sets. Whatever passes on one and fails on the other is a defect your users would have found for you. For background, see our write-ups on testing foldable phones, the earlier Galaxy Z Fold4 launch, and Android 17 on real devices.
Author
Vaishali Vatsayan is a Community Contributor at TestMu AI with 5+ years of experience in copywriting, content strategy, and UX writing for SaaS and AI products. She is skilled in test automation and mobile automation testing across Android and iOS, and specializes in product copy, onboarding flows, microcopy, UI strings, and brand voice. She worked as a Senior Copywriter at Leena AI.
Reviewer
Srinivasan Sekar is Director of Engineering at TestMu AI (formerly LambdaTest), where he leads engineering and open-source initiatives behind the Selenium and Appium automation grid and owns TestMu AI's MCP Server. A committer to Appium and a contributor to Selenium, WebdriverIO, Taiko, and AppiumTestDistribution, he brings over 15 years of experience in quality engineering and open-source technologies. He is the author of the Apress book 'The MCP Standard: A Developer's Guide to Building Universal AI Tools with the Model Context Protocol,' a Certified Kubernetes and Cloud Native Associate, and an international conference speaker. Before TestMu AI he spent over eight years at Thoughtworks as a Principal Consultant and Quality Architect. Srinivasan holds a B.Tech in Information Technology from Anna University.
Did you find this page helpful?
More Related Blogs
TestMu AI forEnterprise
Get access to solutions built on Enterprise
grade security, privacy, & compliance