Skip to the article
On this page
  1. Three different things people call “QR code security”
  2. What can someone read from a Wi-Fi QR code?
  3. Is a QR code that opens an HTTPS website encrypted?
  4. Can a QR code ever carry truly private information?
  5. When should you avoid putting information directly into a QR code?
  6. Frequently asked questions
  7. The takeaway
  8. Sources and limitations

Are QR Codes Encrypted? Encoding, Encryption and HTTPS Explained

By OwnQR · Published · Updated

A normal QR code is not encrypted. It turns information into a machine-readable pattern; it does not automatically hide that information from someone who scans it. If a QR code contains a web address, a compatible scanner can read the address. If it contains Wi-Fi connection details, someone who decodes the symbol may be able to read the network name and password.

A QR code can carry encrypted data, but the encryption must happen as part of a separate system. The square pattern itself does not supply secrecy. This distinction matters if you are printing a QR code on a public sign, giving customers Wi-Fi access, or evaluating a product advertised as an “encrypted QR code.”

For a beginner's explanation of the symbol, see what a QR code is and how it works. Here we focus on what the pattern reveals and what actually protects its contents.

Three different things people call “QR code security”

LayerWhat it doesDoes it hide the QR contents?
QR encodingRepresents text, bytes or a URL as modules within a standard QR symbolNo. A compatible reader decodes the encoded message.
Content encryptionScrambles the information before it is placed in the code; a separate application and key may be needed to read itPotentially, yes—if an appropriate cryptographic system is used correctly.
HTTPS/TLS after a scanProtects communication between a browser or app and a server when a secure connection is establishedNo. It protects the network connection, not the printed QR message.

These layers can coexist without becoming the same feature. You can encode a perfectly ordinary HTTPS link into a QR code: the URL in the square is still readable. Only when the browser opens the link does a secure HTTPS connection become relevant. The TLS 1.3 specification describes protection for communication between peers. It does not claim to hide printed QR content; the QR image remains readable because encoding and transport encryption are separate steps.

Encoding is not encryption

Imagine writing https://example.com/menu on paper. Representing that same address with black and white QR modules changes how the address is stored, not whether it is secret. A QR scanner reverses that representation. It does not need a secret cryptographic key to decode an ordinary standards-compliant QR symbol.

A QR generator may choose among versions, error-correction levels and mask patterns. These affect the QR symbol, but none is a substitute for encryption. DENSO WAVE publishes a standards overview of QR symbology.

What can someone read from a Wi-Fi QR code?

Wi-Fi QR codes may contain connection details such as a network name and password. When those details are included as readable text, a compatible reader can recover them: the QR pattern is not itself an encryption layer. A phone may offer to connect to a network, depending on the operating system and scanning software. This does not establish how any particular device behaves.

Practical rule: Treat a publicly displayed Wi-Fi QR code as a way of sharing the password. For a shop, cafe or waiting area, use a dedicated guest network with appropriate access restrictions rather than displaying credentials for the primary internal network. Do not put other secrets into QR codes under the assumption that the squares make them unreadable.

If you want to create a guest-network code, OwnQR provides a Wi-Fi QR code tool. The password it encodes should be treated as visible to anyone who can read the code; the tool is not an encryption feature.

Is a QR code that opens an HTTPS website encrypted?

The website connection may be encrypted; the QR code is not. A direct URL QR code contains an address such as https://example.com/help. Anyone who scans it can see that address, even before they open a browser.

A hosted or redirect-based QR code usually contains a different, shorter address. After scanning, the browser requests that short address; a service may then redirect the visitor to a destination configured on the server. That does not make the short address encrypted. It means the final destination may be managed by a service instead of being written directly into the original pattern.

There are two useful checks here. First, verify that the displayed or previewed address belongs to the organization you intended to visit. Second, remember that a secure browser connection does not by itself prove the organization behind a page is trustworthy. Whether the destination is trustworthy is a separate question from whether a QR symbol encrypts data.

Can a QR code ever carry truly private information?

Yes, but privacy comes from the system around the code. For example, a controlled application could encrypt a message before passing the encrypted bytes to a QR encoder. A compatible receiving application would then need the correct key to decrypt the message. Scanning the symbol with a generic QR reader may reveal encrypted-looking data without making it intelligible.

That workflow requires decisions about key management, recipient access, encryption software, and what should happen when a key is lost or compromised. Simply choosing a dynamic QR code or using a mask pattern does not provide those protections.

Another technology sometimes confused with encryption is a digital signature. A signature is generally used to help a receiving system check authenticity and detect changes; it does not necessarily hide readable content. The two functions solve different problems and may be combined by a system that needs both.

What about SQRC?

DENSO WAVE describes SQRC as a specialized QR-related format with public and restricted data areas that require supported readers. DENSO explicitly cautions that its reading restriction does not guarantee the security of the coded data. See DENSO's SQRC explanation. SQRC is not what an ordinary consumer QR generator produces by default, and it should not be treated as proof that all QR symbols encrypt their contents.

Encryption is not the same as copy resistance. Even when an application encrypts content before encoding it, someone can still photograph or reproduce the QR image; whether that duplicate grants useful access depends on the receiving system. Our guide to copying and cloning QR codes explains that distinction. Treat authorization and key management as application responsibilities, not features of the printed square.

When should you avoid putting information directly into a QR code?

A useful question is: Would you be comfortable printing these exact bytes as text on the same sign? If the answer is no, storing them in an ordinary public QR code is usually the wrong approach.

For a public menu, business website, or general information page, a URL is normally appropriate. For a guest Wi-Fi network, deliberately sharing access credentials may be appropriate if the network is separated and managed. For confidential records, authentication tokens, or a personal identifier that should not become public, use a properly designed application and access-control system. Whether a link eventually requires authentication is determined by the server, not by the QR pattern.

Frequently asked questions

Can someone get your information from a QR code?

They can read the information encoded in that symbol with compatible software. That is not the same as automatically obtaining all the information on your phone. If the QR contains a URL, opening the URL may create a separate interaction with a website; consider that website and your privacy choices independently.

Can you decrypt a QR code?

Most ordinary QR codes are decoded, not decrypted. A scanner turns the modules back into the encoded URL or text. If the creator separately encrypted the content before encoding it, reading the original message may also require a decryption key and suitable software.

What are the risks of using a QR code?

Ask whether the encoded information should be public and whether the destination is legitimate. For destination risks, separately assess whether the URL and the website it opens are trustworthy.

Where should you not use QR codes?

Do not use an ordinary public QR code to conceal confidential details: anyone who can decode it may read its payload. If the concern is a misleading destination, assess the URL and the website rather than treating QR encoding as encryption.

The takeaway

A normal QR code is a readable data container, not an encrypted vault. If you need secrecy, encrypt the content outside the QR format and control who can decrypt it. If you only need a convenient way to share a URL or guest-network details, use the QR code for that purpose—but assume its encoded content can be read by others.

Sources and limitations

Browse all QR code guides