> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/booking-links/qr-codes.md).
# QR codes
Share a personal booking link on a business card, event stand, or printed handout. Scanning its QR code opens the booking page with current availability.
## Download a code
1. Open **Booking links → My Personal Links**, or **All Members Links** if you manage a teammate's link.
2. Choose **QR code** from the link's actions. You can also open it from the link editor.
3. Check the meeting, host, and workspace shown in the dialog.
4. Download **PNG** for a ready-to-use image or **SVG** for artwork that needs to scale.
5. Scan the code and check the booking page before sharing it.
Download the code as SVG or PNG, then test a scan before printing.
The link owner and workspace admins can generate codes. QR sharing is available for personal booking links, including links managed for other members. Group links and routers do not have this action.
## Keep printed codes working
The QR code follows the booking link itself. Changing its slug or the host's username keeps an existing printed code pointing to that same link at its new address. Reusing the old slug for a different link does not change the code's destination.
Deleting the link makes its code unavailable. If the link has no available times, visitors see the normal booking experience for that situation. A QR code does not reserve time or bypass the link's scheduling rules.
Codes have no scheduled expiry. Keep the white border intact when placing one in a design, and test a sample at its final printed size before producing a batch.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.distro.so/booking-links/qr-codes.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
