# Multi-Page Application \(MPA\)

A multi-page application uses browser document navigation to request and load a new HTML document for each primary route transition.

- Type: framework
- Domain: Engineering & architecture
- Level: Intermediate
- Last reviewed: 2026-09-23
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/multi-page-application/>)

## What it means

A multi-page application \(MPA\) is a web delivery architecture where navigation between primary URLs loads new documents from a server or static host. Each response can contain complete usable HTML and may add JavaScript for local interactions. MPA does not mean a site is static, uninteractive, or rendered from hand-written files.

## Why it matters

Document navigation provides built-in URL, history, loading, focus, and failure behavior with a small client runtime. It can simplify delivery and resilience, although full navigations may reset transient state and repeat shared resource work.

## When to use it

Use an MPA for content-led sites, forms, commerce, or workflows whose routes can operate as independent documents. Add client-side islands or enhanced navigation selectively when measured interaction needs justify the additional state and complexity.

## How it works

1. Each meaningful route resolves to a server or statically generated document.
2. A link or form action starts the browser's standard navigation lifecycle.
3. The server or host returns HTML plus referenced styles, scripts, and media.
4. The browser replaces the active document and initializes its resources and accessibility state.
5. HTTP caching and shared assets reduce repeated transfer across navigations.

## A practical example

A public-service application uses a separate server-rendered document for each eligibility step. Standard forms still submit and recover without client JavaScript, while a small script enhances postcode lookup without taking over routing.

## Where it breaks

Full navigations can interrupt media, clear in-memory state, and feel slower when responses or assets are poorly cached. Complex real-time workspaces may need more client coordination, while careless duplication can increase server-template maintenance.

## Common mistakes

- Describing every server-rendered site as static or noninteractive.
- Reloading large uncached assets on every route.
- Storing necessary workflow state only in the outgoing document.
- Adding SPA-style navigation without preserving the MPA's resilience and semantics.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/multi-page-application/#visualization-multi-page-application>)

## Sources

1. [HTML Standard: Loading Web Pages](<https://html.spec.whatwg.org/multipage/browsing-the-web.html>) — WHATWG · Living web standard
2. [Rendering on the Web](<https://web.dev/articles/rendering-on-the-web>) — web.dev · Official technical guidance

## Related topics

- [Single-Page Application \(SPA\)](<https://wiki.soroush.uk/topic/single-page-application/>)
- [Server-Side Rendering \(SSR\)](<https://wiki.soroush.uk/topic/server-side-rendering/>)
- [Static Site Generation \(SSG\)](<https://wiki.soroush.uk/topic/static-site-generation/>)
