Direct answer

The short version

The browser Back button is disabled when the active tab has no earlier page entry it can revisit. This commonly happens because the page opened in a new tab, the relevant navigation happened in another tab or window, the tab is newly created, or the previous page was closed rather than navigated away from.

Key takeaways

  • Back history belongs to the active tab, not the entire browser window.
  • Opening a link in a new tab starts or reuses a different history context.
  • A closed tab requires recovery, not normal Back navigation.
  • Some web apps manage routes through the History API, so behavior can depend on the site.

Start with the active tab’s history

Read the tab title and address bar. A similar page in another tab can make it seem as though Back forgot a visit. Switching tabs does not merge their session histories.

If the target page opened in a new tab, the original page is often still present in its old tab. Search open tabs before opening another copy or searching the full browser History.

  • Wrong active tab: use the tab strip or tab search.
  • Page opened in a new tab: return to the source tab.
  • Tab was closed: use Reopen Closed Tab.
  • Older visit: search browser History.
  • Previous location was another app: use app switching or cross-app history.

Understand redirects and web-app routing

Browsers maintain a session-history list for each browsing context. Websites can add an entry with pushState or update the current entry with replaceState. A site that replaces state may not create the extra Back stop you expected.

Redirects, authentication flows, and security policies can also collapse or skip intermediate pages. Do not assume every visible screen creates a separate durable history entry.

Use the recovery tool that matches what happened

If the page is open, use tab search. If it closed recently, reopen the closed tab. If it was visited earlier, use browser History. If it was a durable source, use a bookmark or source note.

ReturnFast can select an existing exact-URL tab in Chrome, Brave, and Edge when it appears in the recent cross-app trail. It does not replace browser History or guarantee reconstruction of a missing tab.

  1. Search open tabs

    Find the existing page without creating a duplicate.

  2. Check recently closed

    Recover the tab object when closure caused the loss.

  3. Search History

    Find an older visited URL when the tab is gone.

Further reading and product details

MDN guide to session historySee how web apps add and replace browser history entries.Google Chrome History helpRecover an older visited page when Back is unavailable.Back vs Reopen Closed TabChoose navigation or recovery based on what happened to the page.

Frequently asked questions

Why is Back disabled after opening a link?

The link may have opened in a new tab, leaving the source page in the original tab rather than adding an entry to the new tab.

Can a website change how Back behaves?

Yes. Web apps can add or replace session-history entries, and redirects can affect which earlier entries remain meaningful.

Does browser History contain the same list as the Back button?

No. Back follows the active tab’s session history. Browser History is a broader record of visited pages.