Updated 25 October 2026 Awwwards ● The FWA ● CSS Design Awards

Exhibita

A journal of the best-designed websites

The short version

Out: many colours at once.In: a real footer.

many colours at once fell from 28% to 20% of award winners in a year, while a real footer went from 6% to 11%.

01 — The short answer

What's hot

Five countdowns: what the winners look like, the colours they use, what moves, how people are got around, and what is climbing fastest. Every row shows a winner carrying it, and says whether it is rising or falling.

02 — Which way this is heading

In & Out

Down: giant headlines, 25% to 15%. Up: true depth, 33% to 40%. Every movement in the record, counted two independent ways, with the ones both counts agree on marked.

03 — What they have in common

Trends

The whole record read at once: which traits cluster, which have moved, and what separates one kind of site from another.

04 — One list, eight ways

Wire

Today's arrivals drawn eight different ways — marquee, poster, mosaic, terminal, contact sheet — and what each arrangement does to the same material.

05 — Browse by kind of business

Categories

Shops, museums, restaurants, studios — 20 kinds of site, because a bakery and a bank are not the same brief and should not arrive at the same page.

06 — Browse by decision

Craft

Colour, structure and motion — the three decisions every project makes, and what each one signals about the kind of site you are making.

07 — Showing your own work

Portfolios

A portfolio that wins is built out of pages, not spectacle — a real project page and a real about page beat every effect client work reaches for. Six ways of putting the work in front of someone.

08 — The first screen

Landings

The landing pages the galleries are showing this week, and what a winning first screen ships before any JavaScript runs.

09 — What the first screen says

Words

The headlines off 307 winners' own home pages, word for word. 78% of them address nobody — no you, no we — which is the opposite of every instruction ever given about writing for the web.

10 — The screen it is really seen on

Phone

What phone-first work does differently — the order of things rather than the look of them — and which kinds of site fall apart when the wide composition goes.

11 — Ranked by the jury

Top rated

Every recent winner in the order the jury scored it, this week's arrivals, and the live board from five award sources.

12 — Every Site of the Year

Canon

The top prize on the web, all of it in one gallery. Scroll to the oldest and you are looking at the flat web of a decade ago.

13 — Who keeps winning

Studios

The all-time table: which studios clear the bar again and again, where they are, and the different strategies behind it.

14 — Sites taken apart

Case files

Winners looked at closely — including the ones that took the top prize with almost none of the technology everyone assumes is required.

15 — How people get around a page

Navigation

Which patterns are rising, which are going, and what a route people have to learn really costs — measured against the jury's own usability marks.

16 — Presenting yourself

Designers

A grid of thumbnails to browse on 21% of designers’ own sites against 6% of studios’, and 3D on 22% against 34% — with real designers explaining their own practice, and a live shelf of personal sites.

17 — What tomorrow looks like

Futurism

Work about AI, space and the synthetic has a shared look — and it is not the dark, glowing one every brief reaches for first.

18 — How the numbers are made

How it's judged

Design 40, usability 30, creativity 20, content 10. Eighteen jurors, the three most extreme scores discarded, and a five-day clock.

19 — What they are built with

Stack

How movement gets choreographed, how depth gets drawn, and why those skills are becoming teachable rather than rare.

20 — The work ahead

Careers

Which design jobs are growing, which are shrinking, and roughly when.

The story 25 October 2026

Apple’s Folding Phone Arrives, and a Web Page Can Learn Where the Fold Is

iPhone Duo went on sale on Friday with Safari 27.1 on it. Held half open, like a book, its inner screen has two halves with the fold between them. A page can now ask the browser whether the phone is folded and how wide each half is, and put one column on each side, so that no photograph or line of text runs across the crease. Chrome on Android folding phones has done this since last year.

The same page on a half-open iPhone Duo

Laid out as one wide screen

When the browser reports the phone folded: one column each side

An illustration. Chrome on Android folding phones has told a page which side of the fold it is on since the middle of 2025. In Safari 27.1 the same measurements are a developer preview, switched off until the phone’s owner turns them on in Settings.

Apple’s first folding phone went on sale on Friday. Closed, iPhone Duo has a 5.4-inch screen on the front, like any phone. Opened, the inside unfolds to 7.6 inches. Held half open, like a book, that inner screen has a left half and a right half with the fold running between them. Safari 27.1 shipped with it; the WebKit team, which builds Safari, opens its notes for the release with “Today iPhone Duo arrives, and with it, Safari 27.1.”

Safari itself already uses the two halves. When the phone is half open, “Safari 27.1 automatically shows PDFs as two pages side by side,” one page to each half, like an open book. Web pages can now do the same. CSS, the language that sets how a page looks, has long let a page ask the browser a question about the screen, such as whether it is as narrow as a phone, and change its layout on the answer. The new question is called device-posture, and the answer is either folded or continuous, the standard’s word for flat. WebKit’s own example answers folded with two equal columns, each the width of one half of the screen, so that the fold falls in the gap between them and nothing is printed across it.

Read the full storyClose

A second set of measurements tells the page exactly where each half is. In WebKit’s words, “It describes the ‘segments’ of the display — the separate portions on either side of the fold.” Six values give the width, the height and the position of each half. A designer can put the photograph on the left half and the caption on the right, or the menu on one side and the article on the other, with the gutter set on the fold itself.

None of this is Apple’s alone. Both questions come from a draft web standard, the Device Posture API, whose current text at the W3C, the body that writes web standards, is dated May of this year. The draft says what it is for: “The main interest in knowing the posture of a device is to enable new user experiences with responsive design.” Chrome on Android folding phones has answered the posture question since early 2025 and reported the two halves since the middle of that year. Firefox does neither.

In Safari 27.1 the two questions are “a developer preview behind feature flags,” switched off until the owner of the phone turns them on in Settings. A site can be built and tested for the Duo today, but it cannot yet count on being told about the fold. What every site meets in the meantime is a very wide phone. A single Safari window on the Duo can be anywhere from 382 to 951 pixels across, depending on which screen is in use and how the phone is held, and the inner screen is treated as one wide screen with the crease running through the middle of whatever is on it.

Why it mattersFor the first time an iPhone can hold a web page open like a book, and a designer can decide what sits on each side. Few visitors will have one this year, and the fold is reported to a page only when the owner switches it on, so the habit to start now is simpler: at wide phone sizes, keep the headline, the face in the photograph and the button away from the middle of the screen, where the crease of a half-open Duo falls.

Sources: WebKit: Features for Safari 27.1 (23 October 2026) · Apple Newsroom: iPhone Duo arrives at Apple Store locations worldwide · Apple Newsroom: Open up to new possibilities with iPhone Duo (display sizes) · W3C: Device Posture API (Candidate Recommendation Draft, May 2026) · MDN: device-posture media feature · Chrome for Developers: the Viewport Segments API shipped in Chrome 138 (June 2025) · MDN browser compatibility data: media features