Six months ago we published a list of 12 web design trends for 2026. Now, halfway through the year, the honest reality check: bento grids and dark mode are still winning, kinetic typography is more polish than substance, 3D and WebGL turned out to drain performance budgets in ways most teams underestimated, AI-driven personalization broke against GDPR, and two trends nobody predicted in January became the actual story of 2026 web design: AI readability layers (llms.txt, agents.json, schema markup) and anti-grid brutalism as a counter-movement to bento. If you are planning a redesign in the second half of the year, this is the list to optimize against.
In January I wrote a piece for studiomeyer.io listing 12 web design trends for 2026. It became our highest-cited blog post of the year, picked up across Bing Copilot, ChatGPT, Perplexity and Grok, with 347 citations across the German, English and Spanish versions combined. Plenty of time has passed to check what actually held up, what was overrated, and what shifted underneath while everyone was watching the obvious moves. This is that check.
Half the original list is doing exactly what I expected. A quarter overpromised. A quarter underdelivered. And two new trends emerged from the side that nobody on my list predicted in January.
What held up: bento grids, dark mode, design systems
The three calls I made in January that aged well are the structural ones. None of them are flashy. All of them ship in real projects.
Bento grid layouts are now the default, not the exception. Apple kept pushing them across product pages. Google adopted them across the Pixel marketing site. Microsoft, Spotify and roughly half the Y Combinator demo day startups in March all shipped bento-first layouts. We measured 23 percent more scroll depth on bento layouts compared to traditional 12-column grids in our own client work, consistent with the original prediction. The pattern is not a fad. It is the modular content layout that 2026 settled on.
Dark mode as default crossed the threshold I described in January. More than 82 percent of smartphone users now run at least one app in dark mode, OLED savings hold up at the panel level, and the engagement bump on dark-mode-aware sites is real (we measured 18 percent longer sessions across our portfolio). What I underestimated is how much of the work is on the design system side, not the CSS variable side. Building a site that respects dark mode means committing to a token-based color system that handles every component state across both themes. Teams that retrofit dark mode without that foundation end up with broken contrast and hard-to-read text.
Design systems as foundation matched my prediction exactly. Every serious 2026 project we touched has a token system, component library, automated visual regression and a design-to-code pipeline. The teams that skipped this step in 2024 are paying for it now in fragmented redesigns.
What overpromised: kinetic typography, glassmorphism 2.0, organic shapes
Three trends I called confidently in January turned out to be more polish than substance.
Kinetic typography is everywhere as a demo on Awwwards and Dribbble. It almost never ships in production. The reason is simple: animated text fights screen readers, fights search crawlers, and adds layout shift that destroys Core Web Vitals scores. Real teams use it sparingly, on hero headlines and section transitions. The image of a site with dozens of kinetic elements scrolling and animating did not become the default. It became the demo reel.
Glassmorphism 2.0 survived but in a more restrained form than the January trend pieces predicted. The CSS backdrop-filter: blur() is still computationally expensive, especially on Android mid-tier devices. Teams that went heavy on the effect saw 15 to 30 percent FPS drops on real user devices. The aesthetic survived in navigation bars, modals and feature cards. It did not become the dominant treatment for hero sections.
Organic blob shapes and asymmetric containers had the strongest gap between trend articles and shipping reality. They show up on landing pages where the brand can afford the playfulness. They almost never ship on B2B SaaS, e-commerce or any conversion-critical flow. The "hero with a giant blob" pattern is a 2024 trend that 2026 articles kept recycling without checking which industries actually use it.
What underdelivered: 3D/WebGL, AI personalization, sustainable web design
Three calls I made too optimistically.
3D elements via WebGL were supposed to become standard. They did not. The math is brutal: a site with a single Spline scene in the hero loads 800kB to 2MB of JavaScript runtime before the user sees anything. Lighthouse scores collapse. Core Web Vitals fail. Mobile users on 4G drop the page before the WebGL loads. The shipping pattern in 2026 is to use WebGL only when the brand is the experience (creative agencies, fashion houses, art portfolios) and to skip it everywhere else. The "everyone gets a 3D hero in 2026" prediction was wrong. The "creative agencies push 3D harder than ever" prediction was right. They are different sentences.
AI-driven personalization ran into the GDPR wall. The pattern of dynamically rendering personalized content based on tracked behavior works in the US, but in the EU it requires consent flows that destroy the personalization premise. Teams with European traffic stayed on first-party data and cohort-based personalization, which is much more limited than what AI vendors marketed. The trend lives. The implementation is more conservative than 2025 trend pieces suggested.
Sustainable web design got measured but did not get adopted broadly. Tools like Website Carbon Calculator are common in agency presentations. The actual decisions teams make (image weights, JavaScript budgets, hosting choice) still optimize for cost and speed first, sustainability third. The trend is real but it has not yet become a primary buying criterion for clients. Maybe in 2027.
What we missed: AI readability and the anti-grid counter-movement
Two trends nobody on my January list predicted have become the actual story of mid-2026.
AI readability as a design layer. In January, "structured data" felt like a 2024 SEO topic. By April, it became the load-bearing piece of every serious 2026 web project we touched. Schema.org markup, llms.txt files, agents.json, agent-card.json, JSON-LD across pages, structured FAQ blocks. Sites that skipped this layer fell out of AI Overviews on Google, lost ChatGPT and Perplexity citations, and saw measurable traffic drops as more search shifted to AI-mediated answers. We track our own numbers: 2,300 Bing Copilot citations across three months by early May 2026, verified live in the Webmaster Tools dashboard. None of that exists without the readability layer.
If you redesign in H2 2026 and skip AI readability, you are designing a site that humans can use but AI cannot quote. In a year where AI-mediated discovery overtakes a chunk of classic search, that is the equivalent of building in 2010 without considering Google.
Anti-grid brutalism as a counter-movement. This one nobody on my list saw coming. As bento layouts became ubiquitous, a counter-trend emerged: deliberately broken layouts, raw HTML aesthetics, brutalist typography, monospace everything. Sites like The Browser Company's marketing pages, the v0.dev landing page, and most of the indie-hacker SaaS launches in 2026 lean into this aesthetic. It is not retro nostalgia. It is positioning. When everyone else looks like Apple, looking different becomes the differentiator.
This is going to be the design conversation of late 2026 and early 2027. The pendulum swung from custom to template back to custom, and now it is swinging from polished bento to deliberately raw brutalism. Watch which agencies pick which side.
What to optimize for in H2 2026
If you have a redesign in flight, the priority list looks different than it did in January.
Start with AI readability. This is non-negotiable. Schema markup, llms.txt, agents.json, structured FAQ blocks. Without these your site is invisible in AI-mediated discovery, which is now a meaningful slice of B2B traffic. Test by asking ChatGPT, Perplexity and Bing Copilot about your brand. If they cannot quote you specifically, your readability layer is missing or broken.
Then commit to the structural trends that held up: bento grids for content layout, dark mode as a first-class theme, design systems as the foundation everything else builds on. These are not flashy. They compound.
Be conservative with the polish trends. Kinetic typography on hero only. Glassmorphism on navigation and modals only. WebGL only when the brand justifies the performance cost. Treat each as an enhancement, not a foundation.
Watch the brutalism trend. If your competitors are all converging on the same Apple-esque aesthetic, the counter-position becomes valuable. We have not committed to brutalism in our own work yet, but we have prototyped it for two clients in tech-heavy verticals where the audience reads HN and rewards positioning over polish.
What we built around this
For full disclosure: every project we ship at StudioMeyer carries the AI readability layer by default. llms.txt, agents.json, agent-card.json, schema markup, JSON-LD across pages. Every project uses a token-based design system, dark mode as a first-class theme, and bento grids for content layouts when the content has natural hierarchy. We are conservative with WebGL and kinetic typography. We have not built anything brutalist yet.
The result is that our portfolio sites get cited by AI, score well on Core Web Vitals, and survive client redesigns better than templates do. None of that is one trend. All of it is the same thing: optimize for what compounds, skip what is decorative.
If you want a redesign that takes this list seriously, we are here. The first audit is free and includes an AI readability check, a Core Web Vitals run and a design system review.
Originally published on studiomeyer.io. StudioMeyer is an AI-first digital studio building premium websites and intelligent automation for businesses.