---
title: "How to add a Back to menu button to your QR code pages"
description: "Give the pages behind your menu a Back button so visitors can browse several pages from one QR code and return to the menu each time. Where the option is offered, how to label it, and how to build a page whose only way out is back."
canonical: "https://linkbreakers.com/help/article/how-to-add-a-back-to-menu-button"
last-updated: 2026-10-18
---

# How to add a Back to menu button to your QR code pages

> Give the pages behind your menu a Back button so visitors can browse several pages from one QR code and return to the menu each time. Where the option is offered, how to label it, and how to build a page whose only way out is back.

:::try-ai-prompt {"prompt":"Build a menu with three buttons: 'Available homes', 'Opening hours' and 'Contact us'. 'Available homes' opens a multi-link page whose buttons open my floor plan PDFs from the media library, with a 'Back to menu' back button. 'Opening hours' is a thank you page with our hours and a 'Back to menu' back button. 'Contact us' opens a contact card with a 'Back' back button.","target":"assistant","description":"Ask the Assistant to build a menu whose pages each lead back to it."}:::

## Short answer

Open the page step's form, either when you add it or when you edit it, and turn on **Back button** at the bottom of the form, under the page's buttons. Give it a label such as "Back to menu". It works like the browser's back button and returns visitors to the page they came from, so you do not have to wire anything.

The option is only offered where it can work: on a page that some visitor reaches after another page, such as a page behind your menu. On the first page after a scan there is nothing to go back to, so the form does not show it.

The other way back is a connection: drag a step's button back to the multi-link page (the menu) that led to it. The canvas draws this connection as a return curve.

## Quick summary

- **Back button** sits at the bottom of each page step's create and edit form, under its buttons
- It is offered only where a page comes before the step on some route through the workflow. It is not offered on the first page after a scan, even behind conditions
- Visitors see a secondary button with your label ("Back" if you leave it empty), styled from your page theme
- It stays hidden on a visit that came straight from a scan, because there is no previous page
- A page whose only way out is back to the menu (opening hours, a notice, contact details) is a [thank you page](/help/article/how-to-create-a-thank-you-page) with a back button
- A step's button can also be connected to an earlier step, not only to the next one
- If a button is not connected to anything, visitors are sent to the link's [fallback destination](/help/article/what-is-a-fallback-destination-in-linkbreakers)

## How it works

### The back button option

Select a page step on the canvas to open its form in the side panel, or add a new page step. At the bottom of the form, under the page's buttons, turn on **Back button** and type its label (up to 40 characters, "Back" if you leave it empty).

Visitors see the button under the page's main buttons, in a secondary style that follows your page theme's button colour, so it reads as the second choice. Tapping it goes back one page in their browser, to wherever they came from: usually your menu.

It exists on every page step: message pages, menus (multi-link pages), forms, contact cards, social links pages, password pages and thank you pages. Redirects, conditions and Open media steps never show a page, so they have none.

### Where the option is offered

A back button can only do something when a visitor has seen another page before this one. Linkbreakers works this out from your workflow:

| Where the page sits | Back button offered |
|---|---|
| Behind a menu, a form or a password page | Yes |
| The first page right after the scan | No |
| After only conditions or other steps that show nothing, with no page before it | No |
| Reached both straight from the scan and from a menu | Yes, and it shows only to visitors who came from the menu |

If you rewire the workflow so that a page no longer has a page before it, the option disappears from its form. The label you set is kept, and the button comes back once a page comes before the step again.

Even where it is offered, the button hides itself on a visit that came straight from a scan, because going back would leave your pages.

### A page whose only way out is back

Some pages behind a menu do not lead anywhere: opening hours, a short notice, a delivery area. A message page always shows its main button, and that button must lead somewhere. For a dead end, use a **thank you page** with a back button labelled "Back to menu". It has no other buttons and nothing to wire, so the back button is the visitor's only way out.

### Back button or connection?

Use the back button when "go back to where I was" is all you need. Connect a button to the menu instead when the page should always lead to the menu, whichever way the visitor arrived, or when you want the click recorded as a step in the journey. Do not do both on the same page: a back button and a main button that both return to the menu show two buttons doing the same thing.

## How connections work

Every button in a workflow goes to the step it is connected to on the canvas. Most connections point forward, to the next step in the journey. A connection can also point back to an earlier step. When a visitor taps that button, they return to the earlier step, for example the menu.

This turns a straight-line journey into a small site behind one QR code:

| Step | Role |
|---|---|
| Multi-link page | The menu, with one button per section, or a sub-menu listing documents |
| Open media | Opens a PDF, image or video from your media library |
| Redirect | Opens a web page, or a document hosted elsewhere such as a Google Drive link |
| Message page | A short message with one way onward |
| Thank you page | A dead end, with a back button as its way out |
| Contact card | A person's details |

## Step-by-step

1. Open the link's workflow in the dashboard
2. Add a multi-link page as the menu, with one button per section
3. Connect each menu button to the page for that section: another multi-link page, a contact card, a thank you page
4. In each of those pages' forms, turn on **Back button** under the buttons and label it "Back to menu"
5. Save, scan the QR code and tap through each page to check that every "Back to menu" button returns to the menu

## Worked example: a home builder's sales menu

A home builder puts one QR code on a yard sign. Scanning it opens a menu:

- **Multi-link menu** with three buttons: "Available homes", "Opening hours" and "Contact us". It is the first page after the scan, so its form offers no back button
- **"Available homes"** opens a second multi-link page with one button per floor plan. Each button leads to an Open media step that opens the floor plan PDF. A back button labelled "Back to menu" returns to the menu
- **"Opening hours"** opens a thank you page with the sales office hours and a "Back to menu" back button, its only way out
- **"Contact us"** opens a [contact card](/help/article/how-to-create-contact-cards-vcard-in-linkbreakers) with a "Back" back button

For the full PDF setup, see [how to put several PDFs behind one QR code](/help/article/how-to-put-several-pdfs-behind-one-qr-code).

## Frequently asked questions

### Why is there no Back button option in my page's form?

No page comes before this step on any route through the workflow, so a back button could never show. That is the case for the first page after a scan, even when conditions sit in between. Put the page behind a menu or another page, and the option appears.

### Why don't I see the back button when I scan?

You landed on the page straight from the scan, so there is nothing to go back to. Tap through to the page from your menu and it appears.

### Why does my "Back to menu" button open my Google Drive?

The button is a regular button that is not connected to anything, so it sends visitors to the link's fallback destination, which here was a Google Drive folder. Turn on **Back button** in the page's form instead, or drag the connection from the page to the menu step on the canvas.

### How do I make a page whose only button goes back to the menu?

Use a thank you page with a back button labelled "Back to menu". A message page always has a main button that must lead somewhere, while a thank you page has none, so the back button is its only way out.

### Which pages can have a back button?

Every step that shows a page: message pages, multi-link pages, forms, contact cards, social links pages, password pages and thank you pages.

### How do I know a connection goes back to the menu?

The canvas draws a connection to an earlier step as a return curve between the two steps.

### Can I share PDFs from the pages behind the menu?

Yes. Use a multi-link page with one button per document, and connect each button to its own [Open media step](/help/article/how-to-share-media-from-a-qr-code) holding the PDF from your media library. For a PDF hosted on Google Drive, Dropbox or a similar service, connect the button to a redirect step whose destination is its share link instead.

### Can the Assistant add back buttons?

Yes. Ask for "a 'Back to menu' button on the pages behind the menu" and the [Assistant](/help/article/the-assistant-section) turns on the back button where it can show. When a page has nothing before it, the Assistant says so instead of adding a button that would never appear.

## Limits and caveats

- The back button follows the visitor's browser history, so it returns to the page they actually came from
- It is offered only where a page comes before the step, and hidden on a visit that came straight from a scan
- Back button labels are limited to 40 characters
- A button only returns to the menu through a connection if it is connected to the menu on the canvas. Unconnected buttons send visitors to the link's fallback destination
- Test every path after editing the workflow, especially after adding or removing steps

## Last reviewed

2026-10-18