Syntax
history.pushState(state, title, url)
window.addEventListener("popstate", callback)Examples
Changing the URL Without a Page Reload
Updating the address bar and history stack for client-side navigation.
function navigateTo(path) {
history.pushState({ path }, "", path);
renderPage(path); // your own function to update the visible content
}
navigateTo("/about"); // URL changes to /about, no reload happensHandling Back/Forward Navigation
Responding when the user clicks the browser's back or forward button.
window.addEventListener("popstate", (event) => {
const path = event.state ? event.state.path : "/";
renderPage(path); // re-render based on the restored state
});
// Note: pushState() itself does NOT trigger popstate -
// only actual browser back/forward navigation doesBest practices
- Use pushState() for genuine navigation events that should be added to history - use replaceState() instead when updating the URL without adding a new back-button entry
- Always store enough state in pushState()'s first argument to correctly restore the view on popstate, rather than only relying on parsing the URL
- Remember popstate only fires on actual browser navigation (back/forward buttons) - calling pushState() yourself does not trigger it
- Consider a routing library for anything beyond simple navigation - hand-rolled routers can miss edge cases like nested routes or query parameters
Runtime & versions
Browsers and JavaScript runtimes. Feature availability depends on the language and runtime version used by your project; consult the official reference below.
ECMAScript specification