> For the complete documentation index, see [llms.txt](https://docs.codeeqr.com/product-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codeeqr.com/product-docs/questions-and-answers/about-qr-codes-general/difference-between-static-and-dynamic-qr-codes.md).

# Difference between static and dynamic QR codes

A static QR code is a QR code that contains a fixed set of information, which cannot be changed once it has been generated. This type of QR code is usually used to store information such as a website URL or a phone number, which the user can scan and access using a smartphone or QR code reader.

A dynamic QR code, on the other hand, is a QR code that can be edited and updated even after it has been printed or displayed. This is done by using a special URL or a unique ID that is associated with the QR code, which can be used to access and modify the information stored in the QR code. Dynamic QR codes are often used in marketing and advertising campaigns, where the information displayed on the QR code can be updated or changed to reflect the latest promotions or offers.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.codeeqr.com/product-docs/questions-and-answers/about-qr-codes-general/difference-between-static-and-dynamic-qr-codes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
