Web Trends 2025
The Complete Year in Review

At the start of 2025, most of what happened later was already on the roadmap, but the pace caught a lot of teams off guard. This review looks at what changed, what it means in practice, and what to watch in 2026.

How AI changed web development

In 2025, AI tools became part of everyday work for many developers. In the Stack Overflow Developer Survey 2025, 84% of respondents said they use or plan to use AI tools in their development process, and 51% of professional developers use them daily.

GitHub Copilot and React's dominance

AI tooling also strengthens React's lead. A likely reason: React is so widespread in the frontend that the data LLMs learned from contains a lot of React code. Ask Copilot for a solution and you'll often get a React-based answer, even when another tool would fit better.

Local LLMs on the rise

Cloud-based assistants like GitHub Copilot are widely used, but we see growing interest in local Large Language Models that run on the developer's own hardware. They keep code private, work offline and respond with lower latency. That matters most for European companies with strict compliance requirements.

Our main takeaway from 2025: AI speeds up a lot of routine work, but a developer still has to understand the architecture, review what the AI produced, and catch the confident mistakes it makes.

Framework comparison 2025: React, Astro, Svelte and more

React still dominates, but in 2025 the alternatives found their footing. Astro, Svelte, and Qwik each have clear cases where they're a better fit than React, and teams are getting better at recognizing when that applies.

React 19: Server Components become the default

With React 19, Server Components left experimental status and became the recommended default for new projects. The other changes are smaller, but you will notice them in daily code:

• useActionState replaces the old useFormState for Server Actions
• ref as a prop instead of forwardRef, which makes the API much simpler
• use() Hook for resolving Promises in components
• useOptimistic for optimistic UI updates
• Improved hydration with less client-side JavaScript

// React 19: ref as Prop (forwardRef is deprecated)
function Input({ ref, ...props }: { ref?: React.Ref<HTMLInputElement> }) {
  return <input ref={ref} {...props} />
}

// React 19: useActionState for Server Actions
import { useActionState } from "react"
const [state, action, pending] = useActionState(serverAction, initialState)

// React 19: use() Hook for Promises
import { use } from "react"
function Component({ dataPromise }: { dataPromise: Promise<Data> }) {
  const data = use(dataPromise)
  return <div>{data.name}</div>
}

Next.js 15: async everything

Next.js 15 introduced several breaking changes for existing projects. The biggest one: params and searchParams are now async, which changes how dynamic routes work:

// Next.js 15: params is now async (BREAKING CHANGE)
async function Page({ params }: { params: Promise<{ id: string }> }) {
  const { id } = await params  // MUST await
  return <div>{id}</div>
}

// WRONG in Next.js 15 - this no longer works:
function Page({ params }: { params: { id: string } }) {
  return <div>{params.id}</div>  // TypeError!
}

Astro: performance for content sites

Astro kept gaining ground in 2025 and is now a common choice for content-heavy sites. Its Islands Architecture ships zero JavaScript by default and hydrates only the parts that need to be interactive. That makes good Lighthouse scores easier to reach than in a React-heavy setup.

Svelte: performance without a Virtual DOM

Svelte has grown from an interesting experiment into a real alternative. It has no Virtual DOM and compiles components at build time, so its runtime performance is hard to beat. If interaction speed is critical for your project, Svelte deserves a serious look.

Qwik: instant loading

Qwik uses resumability instead of hydration. Pages become interactive without first re-running the component code in the browser. E-commerce and high-traffic applications are the obvious use case. Adoption is still limited.

Core Web Vitals 2025: INP instead of FID

Since March 12, 2024, Interaction to Next Paint (INP) has been a Core Web Vital, replacing First Input Delay (FID) as the responsiveness metric. 2025 was the first full calendar year with INP, and that changes what you need to optimize.

What INP measures

FID only measured the first interaction. INP tracks every user interaction across the whole page visit. A fast initial load no longer covers you: slow button responses or laggy form inputs will drag your score down.

Optimization strategies for 2025/2026

• Scroll-driven animations in CSS instead of JavaScript for fast scroll effects, with an @supports fallback for Firefox
• Lazy loading for images and non-critical components
• Edge computing for fast load times worldwide
• Server-side rendering or static generation where possible
• Bundle splitting and tree shaking to keep JavaScript bundles small

Astro, Next.js 15, and Qwik make good Core Web Vitals easier to reach from the start. Existing applications are the harder case: many need substantial work to meet the INP threshold, especially those with heavy client-side JavaScript.

Design trends 2025: Bento, glass and 3D

Some 2024 patterns settled in 2025, and a few new ones appeared. Both groups favor layouts that organize content well, effects that keep text readable, and depth only where it helps.

Bento Grid: inspired by Apple, adapted everywhere

Bento Grids (named after Japanese lunch boxes) were one of the most visible layout patterns of 2025. Apple has used the approach for years to present product features: modular cards of different sizes, each holding one piece of information, arranged in a clear grid.

Glassmorphism 2025: subtler and more accessible

Glassmorphism (the frosted glass effect with blurred backgrounds) has calmed down since its peak. Early versions were often unreadable. In 2025, teams use it more sparingly, on floating nav bars, modals, and card surfaces where the effect serves a purpose beyond decoration.

/* Glassmorphism 2025: Subtle and accessible */
.glass-card {
  background: rgba(255, 255, 255, 0.05);
  backdrop-filter: blur(12px);
  border: 1px solid rgba(255, 255, 255, 0.1);
  border-radius: 16px;
}

/* Important: Sufficient contrast for text */
.glass-card p {
  color: #e9edf3;
  text-shadow: 0 1px 2px rgba(0, 0, 0, 0.1);
}

3D and immersive experiences

With WebGL, Three.js, and CSS 3D transforms such as rotateX(), rotateY(), and perspective, 3D gained a real foothold in 2025. Product viewers and interactive scroll sequences felt niche two years ago. In some markets they are common now.

Motion design: scroll-driven animations

CSS Scroll-Driven Animations have run in Chrome and Edge since 2023, and Safari added them in version 26 in 2025. Firefox does not ship them by default yet. They need no JavaScript and, when done right, cost almost nothing in performance. Wrap them in @supports so the page still works fully in Firefox, just without the animation.

EAA 2025: accessibility becomes mandatory

Since June 28, 2025, the requirements of the European Accessibility Act (EAA) have applied. The directive entered into force in 2019, and each EU country turned it into national law; in Germany, that is the Barrierefreiheitsstärkungsgesetz (BFSG).

Who is affected?

The rules cover certain products and services for consumers in the EU. Micro-enterprises that provide services are exempt. Affected areas include:

• E-commerce: online shops and booking platforms
• Banking services: online banking, payment systems
• Telecommunications: websites, apps, messengers
• Transport: booking systems, timetable information
• E-books: digital books and reading devices

WCAG as the technical basis

Technically, the EAA relies on harmonised standards. The standard that currently counts in law is EN 301 549 V3.2.1, which builds on WCAG 2.1 Level AA. The new version V4.1.1, based on WCAG 2.2, has been published. If you build to WCAG 2.2 AA, you also meet WCAG 2.1 AA. In practice that means:

• All images need meaningful alt texts
• At least 4.5:1 color contrast for normal text
• Complete keyboard navigation
• Click targets at least 24 × 24 CSS pixels (new in WCAG 2.2)
• No keyboard traps
• Semantic HTML and correct ARIA attributes

For a detailed implementation guide, we recommend our Web Accessibility 2025 Guide.

Native web features: browsers catch up

Browsers closed a lot of gaps in 2025. Features that used to require a JavaScript library are now available natively, which means smaller bundles and less to maintain.

View Transition API: native page transitions

Same-document view transitions reached Baseline in October 2025, when Firefox 144 added them. Transitions between two pages of a multi-page site (cross-document) work in Chrome, Edge, and Safari, but not yet in Firefox. There the page loads without the animation and still works normally.

/* View Transition CSS */
::view-transition-old(root),
::view-transition-new(root) {
  animation-duration: 0.3s;
}

/* Individual element transition */
.hero-image {
  view-transition-name: hero;
}

::view-transition-old(hero) {
  animation: fade-out 0.3s ease-out;
}

::view-transition-new(hero) {
  animation: fade-in 0.3s ease-in;
}

Web AI: AI in the browser

In 2025 Google pushed "Web AI" forward: LLM inference that runs in the browser on the user's device. Requests skip the server round trip, and the data stays on the machine. European companies that have to meet GDPR requirements should keep an eye on it.

Container Queries: responsive by size

Container Queries let components respond to their own size instead of only the viewport. For reusable components, that is a real improvement:

/* Container Query */
.card-container {
  container-type: inline-size;
}

@container (min-width: 400px) {
  .card {
    display: grid;
    grid-template-columns: 200px 1fr;
  }
}

E-commerce innovations 2025

E-commerce made concrete technical progress in 2025, driven by performance benchmarks and the new EAA requirements.

Headless commerce becomes standard

More mid-sized shops separated the frontend from the commerce backend in 2025. Shopify with Hydrogen, commercetools, and Medusa all give you full frontend control while keeping the commerce logic on a stable backend.

Edge-first e-commerce

Rendering at the edge (on Cloudflare Workers or Vercel, for example) puts the server physically close to the user. That shortens server response times, especially for visitors far from the original data center.

AR/VR product experiences

AR product experiences moved past novelty status in 2025. Furniture retailers, fashion brands, and cosmetics companies use AR try-on and 3D product viewers so customers can judge a product better before they buy, which can reduce returns.

Outlook for 2026: what comes next

Based on where 2025 ended up, we expect these developments in 2026:

1. Deeper AI integration

AI tooling will move beyond code completion. AI-powered debugging, automatic accessibility checking, performance analysis, and test generation are already appearing in early form. By the end of 2026, we expect them to be standard workflow features for most teams.

2. WCAG 2.2 gets integrated into EN 301 549

The new version EN 301 549 V4.1.1, based on WCAG 2.2, was published in September 2026. V3.2.1 (WCAG 2.1 AA) remains the legal reference until the EU cites the new version in its Official Journal. Building to WCAG 2.2 AA today prepares you for the switch.

3. Performance needs ongoing checks

New features, scripts, and tracking tools tend to wear down Core Web Vitals over time. Check the Core Web Vitals report in Search Console regularly, not only once before launch.

4. Server Components everywhere

The move toward server-first rendering will continue. Frameworks are getting better at reducing client-side JavaScript without giving up interactivity, and more teams build this way by default.

5. Design system maturity

We expect more companies to invest in proper design systems in 2026: systems that handle accessibility, performance, and visual consistency without custom work on every component. Radix, Ariakit, and shadcn/ui set the bar here.

Frequently asked questions (FAQ)

Where 2025 left things

A lot happened at once: React 19 and Next.js 15 in production, the EAA deadline, the first full year of INP, and AI tooling crossing the line from curiosity to daily use. Not every change needs a response from you, but teams that stayed current had an easier time in the second half of the year.

The tooling is better than before. React 19, Next.js 15, Astro, and modern CSS features make fast, accessible sites easier to build. The hard part is migrating existing codebases and changing habits in teams that set up their processes before these tools existed.

For 2026 we recommend rendering on the server by default, treating performance as a baseline requirement, building accessibility in from the start, and using AI tools to speed up work while people keep doing the thinking. Projects that skip these points usually need more rework later.