Horizon

Samsung's Galaxy Z Fold 8 Bets That Foldables Should Be Wide, Not Tall

A new 4:3 Fold sits beside an Ultra that keeps the familiar shape, and the split says a lot about what Samsung thinks people actually do with a folding phone.

Lin Wei

2 min read ·

1

Samsung used its Galaxy Unpacked event in London on 22 July to change the basic shape of the Fold. Alongside the Galaxy Z Flip 8 and a Galaxy Z Fold 8 Ultra that keeps the familiar tall-and-narrow proportions, the company introduced a Galaxy Z Fold 8 built around a 7.6-inch inner screen with a 4:3 aspect ratio and a 5.5-inch cover display. It weighs 201 grams, which Samsung says makes it the lightest Fold it has made, and starts at $1,899 in the US. All three phones go on sale on 7 August.

Two Folds, two theories of use

The interesting decision is not the wide Fold itself but the choice to ship it next to an Ultra rather than instead of one. The Fold 8 Ultra has an 8-inch inner display at 2504 by 2256 pixels, close to square, and a 6.5-inch cover screen that behaves like a conventional slab phone. It is the thinner of the two when closed, at 8.9mm against the Fold 8's 9.7mm, carries a 200-megapixel main camera, a 5,000mAh battery and a reworked hinge that Samsung says makes the crease less visible. It starts at $2,099, which SamMobile notes is $100 more than last year's equivalent.

The Fold 8 is the opposite argument. Its inner panel is 2448 by 1848 and its cover screen is short and broad, which makes the closed phone feel more like a passport than a remote control. The trade-offs are visible on the spec sheet: dual 50-megapixel cameras rather than a telephoto, a 4,800mAh battery, and a thicker closed profile. Both phones use the same Snapdragon 8 Elite Gen 5 for Galaxy chip and ship with Android 17.

Read together, the line-up says Samsung no longer thinks one Fold fits everyone. The Ultra is for people who mostly use the outside screen and unfold occasionally. The Fold 8 is for people who unfold to watch, read and browse, and who want the inside to be the point.

Why 4:3 matters more than it sounds

Aspect ratio is a design decision that cascades. A near-square inner screen is good for two apps side by side and awkward for almost everything else: video gets thick letterbox bars, and many apps simply stretch a phone layout across a space it was never designed for. A 4:3 landscape panel is the shape of most tablets, so the inner display of the Fold 8 inherits layouts developers have already built and tested. Video fills more of the screen, documents read like documents, and games designed for tablets need less adaptation.

The cover screen is the riskier half. Android apps are tuned for tall, narrow phones, and a broad outer display will expose every layout that assumes a fixed width-to-height ratio. Samsung's own apps will be fine; third-party apps that hard-code breakpoints will not, at least at first. The quality of the folded experience will depend on how many developers bother to test for it.

What is still unclear

  • Durability of the lighter build. Samsung has shaved weight and thickness on the inner fold; how the hinge and panel hold up after a year of use is a question no launch event answers.
  • Whether wide sells. Book-style foldables have stayed niche partly because of price. Splitting the line-up gives Samsung a clean experiment, and the sales mix between the two Folds will be the most honest market research the category has had.
  • Price creep. With the Flip 8 at $1,199 and the Ultra $100 dearer than its predecessor, foldables are moving away from the mainstream, not towards it.

The wider Fold is the more thoughtful product, because it starts from what people do with a big screen rather than from how small the folded phone can be. Whether that thoughtfulness survives contact with Android's long tail of apps is the real test.

Sources

Responses (1)

Sign in to leave a response.

  • Amira Zainal

    The cover screen point applies to the web too. Plenty of sites still pick layouts from device width alone, and a short, broad viewport is exactly where those assumptions fall over. Container queries cannot arrive in production CSS fast enough.

More from Lin Wei

Recommended from Horizon