QR Code Generator
Private by design. Your text, Wi-Fi password, and contact details are turned into a QR code inside this browser. Nothing is uploaded to a server, nothing is stored, and nothing leaves this page. Close the tab and it is gone.
Encoded text
Last reviewed: 20 November 2026. Reviewed every 180 days; next review due 19 May 2027.
How to use the QR Code Generator
This free QR code generator makes a QR code in your browser, with nothing uploaded to a server. Pick a content type, fill in the details, and the code appears at once. It updates live as you type, so there is no button to press and no form to submit.
- Pick a content type. Use the three tabs at the top of the tool: Text or link, Wi-Fi network, or Contact (vCard). The form below the tabs changes to match.
- Enter your content. For text or a link, type or paste it into the box. For Wi-Fi, enter the network name, the password, and the security type. For a contact, enter at least a first name or a last name, plus any phone number, email address, or organization you want on the card.
- Pick an error correction level. The four choices sit under the form: L (Low, 7 percent), M (Medium, 15 percent), Q (Quartile, 25 percent), and H (High, 30 percent). Medium is selected by default and suits most uses. The percentage is the share of the code that can be damaged or hidden while the code still scans.
- Read the result. Under the code you will see its version, its size in modules, its error correction level, and how many bytes it holds. The Encoded text box shows exactly what is inside the code, character for character.
- Download the PNG. Pick a size (512, 1024, or 2048 pixels) and press Download PNG. The file is a square image with a white border around the code, ready to print or paste into a document. It is drawn at the largest whole-module size at or below the size you pick, so every module stays a whole number of pixels and the edges stay sharp: a 2048-pixel download of a version 2 code comes out 2046 pixels across, because 33 cells (25 modules plus the 4-module white border on each side), at 62 pixels each, make 2046. Use Copy encoded text when you want the text itself, for example to paste a Wi-Fi string into a message.
A short link makes a small, sparse code that scans from a distance. A long paragraph makes a dense code that needs to be printed larger. If the code looks crowded, shorten the text or use a shorter link before you print it. Always scan a printed test copy at the real size before you print a batch: a code that scans on a bright screen can fail on paper if it is too small or the contrast is weak.
For a link, include the https:// part so phones open it in the browser. A bare address such as toolselite.com/ still encodes fine, but some camera apps treat it as plain text instead of a link. The ZXing barcode project, whose format guide is the reference most generators follow, says to include the protocol to make sure the text is recognized as a URL.
How it works
The QR code was developed in 1994 at Denso Wave in Japan by a two-person team led by engineer Masahiro Hara. Its original job was tracking car parts on factory floors, where the linear barcodes of the day held only about 20 characters each. QR stands for Quick Response: the code was built to be read fast, from any angle. Denso Wave kept the patent but declared it would not exercise the rights, so anyone can make and use QR codes freely. The symbology became the international standard ISO/IEC 18004, first published in 2000.
Every QR code is a square grid of dark and light modules. The grids come in 40 versions. Version 1 is 21 by 21 modules, which is 441 modules in total. Each version adds 4 modules per side, so version 2 is 25 by 25 (625 modules) and version 40, the largest, is 177 by 177 (31,329 modules). This tool picks the smallest version that fits your content at the error correction level you chose. Short content gets a small code; long content steps up through the versions until it fits.
Your text is encoded in byte mode, the mode that handles any text: web addresses, sentences, accented characters, and emoji. Each character becomes its UTF-8 bytes, so an accented letter such as e with an acute accent takes 2 bytes and an emoji takes 4. The encoder writes a 4-bit mode indicator (0100 for byte mode), then the byte count, then the bytes themselves. Versions 1 to 9 use an 8-bit count field and versions 10 to 40 use a 16-bit count field, which is one reason a code can jump a version when the text grows past a boundary.
After the data comes the error correction. QR codes use Reed-Solomon error correction, the same family of codes used on CDs and in deep-space links. The encoder adds extra codewords computed from your data, so a reader can rebuild the original text even when part of the symbol is scratched, stained, or covered. The four levels trade capacity for toughness:
| Level | Name | Damage it recovers | Best for |
|---|---|---|---|
| L | Low | About 7 percent | Short links shown on a clean screen |
| M | Medium | About 15 percent | Everyday use: menus, flyers, business cards |
| Q | Quartile | About 25 percent | Codes that will be handled, folded, or rained on |
| H | High | About 30 percent | Outdoor signs, packaging, and industrial labels |
Higher levels need more room for the extra codewords, so the same text makes a bigger code at H than at L. That is the whole trade: toughness costs space.
A worked example shows the arithmetic. The text "Hello, world!" is 13 bytes. At level M the encoder writes 4 mode bits, an 8-bit count, and 13 times 8 data bits, which is 4 plus 8 plus 104, or 116 bits. A version 1 code at level M holds 16 data codewords, which is 128 bits, so the text fits with room to spare. The encoder adds a 4-bit terminator (120 bits), then one pad byte, 236, to reach exactly 128 bits. Ten error correction codewords are computed for the single block, giving 26 codewords in total. At level H the same text does not fit version 1, which holds only 7 bytes at H, so the encoder steps up to version 2, which holds 14 bytes at H. You can watch this happen in the tool: type "Hello, world!", switch the level from M to H, and the version line changes from 1 to 2.
Once the codewords are ready, the encoder lays them into the grid in a zigzag pattern, skipping the function patterns: the three finder patterns in the corners, the timing patterns that run between them, the alignment patterns that appear from version 2 upward, and the format and version information areas. A dark module sits at a fixed spot beside the bottom-left finder pattern. Then the encoder tries all eight mask patterns and keeps the one with the lowest penalty score, a measure of how hard the pattern is for a scanner to misread. The mask number is shown under your code.
The finished code is drawn with a quiet zone, a blank white border four modules wide on every side. Scanners need that border to tell where the code ends. The PNG download includes it, so never crop the image tight to the black squares.
The largest possible QR code, version 40 at level L, holds 2,953 bytes of text, or 7,089 digits in numeric mode, or 4,296 characters in alphanumeric mode. This tool encodes in byte mode, so its limits are the byte column of the table below. The table lists byte capacities from Thonky's character capacities table, which covers all 40 versions.
| Version | Size (modules) | L (7%) | M (15%) | Q (25%) | H (30%) |
|---|---|---|---|---|---|
| 1 | 21 by 21 | 17 bytes | 14 bytes | 11 bytes | 7 bytes |
| 2 | 25 by 25 | 32 bytes | 26 bytes | 20 bytes | 14 bytes |
| 3 | 29 by 29 | 53 bytes | 42 bytes | 32 bytes | 24 bytes |
| 4 | 33 by 33 | 78 bytes | 62 bytes | 46 bytes | 34 bytes |
| 5 | 37 by 37 | 106 bytes | 84 bytes | 60 bytes | 44 bytes |
| 10 | 57 by 57 | 271 bytes | 213 bytes | 151 bytes | 119 bytes |
| 20 | 97 by 97 | 858 bytes | 666 bytes | 482 bytes | 382 bytes |
| 40 | 177 by 177 | 2,953 bytes | 2,331 bytes | 1,663 bytes | 1,273 bytes |
The encoder in this tool is built into the page: it is a byte-mode QR Code Model 2 encoder written for Tools Elite, following the algorithm of Project Nayuki's qrcodegen library and the ISO/IEC 18004 rules. It runs entirely in your browser with no library fetched from a server and no data sent anywhere. Like our password generator, it keeps everything on your device by design. Every code it produces was verified against two independent encoders and decoded back to the exact input text before this page was published; the test log is in the tool's build notes.
What your result means
The lines under your code describe the code the encoder built. Each one answers a practical question.
Version. The size class of the code, from 1 to 40. A lower version means a smaller, sparser code that scans more easily. If your code lands at version 10 or above, consider whether the content can be shorter: a long web address can often be replaced by a short link, and a paragraph can often be trimmed to the sentence that matters.
Size in modules. The grid dimensions, such as 25 by 25. Multiply the side by the version rule to check it: version 7 is 45 by 45, which is 2,025 modules, because 21 plus 6 times 4 equals 45. The printed size of each module is what decides how far away the code scans, so a dense code needs a bigger print.
Error correction level. The level you picked, with the share of damage it recovers. The level is written into the code itself, in the format information beside the finder patterns, so any scanner can read it. If you print the code and it will live outdoors or on a package that gets handled, H is worth the extra density. For a code on a clean screen, M is plenty.
Bytes used. The count of UTF-8 bytes in your content, against the capacity of the version it landed in. For example, a 23-byte link at level M lands in version 2, which holds 26 bytes, so the line reads "23 of 26 bytes used". If you are near the top of a version, adding a few characters will push the code to the next version and visibly densify it.
Mask pattern. A number from 0 to 7. The encoder tried all eight masks and kept the one with the lowest penalty score. You do not need to choose it or understand it; it is shown so the code is fully described.
Dark modules. The count of black squares in the grid, out of the total. It is a fingerprint of the exact code: the same text, level, and mask always produce the same count. If two codes for the same text ever showed different counts, one of them would be wrong.
Encoded text. The exact string inside the code. For text mode it is what you typed. For Wi-Fi and contact modes it is the formatted record the tool built from your fields. Read it before you print: a wrong character here is a wrong code, and it is much cheaper to catch on screen than on a printed sign.
If the tool shows an error instead of a code, it says what is wrong. The usual causes are an empty field (a blank text box, a missing network name, a contact with no name) or content too long for the largest code at the level you picked. The message names the limit: at level H the largest code holds 1,273 bytes, so a 3,000-byte text cannot fit at H and the fix is to shorten the text or drop to a lower level.
Wi-Fi and vCard formats explained
A QR code holds plain text. Phones act on it because the text follows a format the camera app recognizes. Wi-Fi codes and contact codes are just two well-known formats written as text.
Wi-Fi codes
A Wi-Fi code holds one line of text in the format proposed by the ZXing barcode project. It looks like this:
WIFI:T:WPA;S:mynetwork;P:mypass;;
Each field has a job. T is the security type: WPA, WEP, WPA2-EAP, or nopass for an open network. S is the network name (the SSID), and it is required. P is the password, left out when the network is open. H:true marks a hidden network, one whose name the router does not broadcast. The record ends with two semicolons. The ZXing guide says the order of the fields does not matter.
There is no WPA2 or WPA3 value in the ZXing list. WPA, WPA2, and WPA3 home networks all use T:WPA, which is what this tool writes when you pick the WPA option. Some Android code defines an SAE value for WPA3, but ZXing does not list it and iPhone behavior with it is not documented, so the safe choice is WPA, tested on both platforms before you print.
Five characters are special in this format: the backslash, the semicolon, the comma, the double quote, and the colon. If your network name or password contains one, the tool escapes it with a backslash, as the ZXing guide requires. A network called Cafe;Bar with the password p:a,ss becomes:
WIFI:T:WPA;S:Cafe\;Bar;P:p\:a\,ss;;
That string is 35 bytes long and makes a version 3 code at level M, which holds 42 bytes. A value made only of hexadecimal digits, such as the network name ABCD or the password 12345678, is wrapped in double quotes so a reader does not mistake it for a hex key, again following the ZXing guide. Its example is the name "ABCD".
Two warnings matter. First, the password sits in the code as plain text: anyone with a QR reader can read it. Treat a printed Wi-Fi code the way you would treat the password written on a card. Second, the code is static. If the password changes, the printed code is wrong and the only fix is a new code. A guest network whose password rarely changes keeps a sign valid longer.
When a guest scans the code, a modern phone offers to join the network instead of showing the text. The ZXing guide labels the format for Android and iOS 11 and later. If the phone shows only text, the string is probably wrong: decode the code with any QR reader, compare it with the table above, and check the semicolons at the end.
Contact codes (vCard)
A contact code holds a vCard, the electronic business card format defined by RFC 2426. Version 3.0 is the most widely supported version, so this tool writes 3.0. A vCard must contain the FN, N, and VERSION fields; this tool always writes all three. A full card looks like this:
BEGIN:VCARD
VERSION:3.0
N:Doe;Jane;;;
FN:Jane Doe
ORG:Acme Inc
TEL:+1-212-555-1212
EMAIL:jane@example.com
END:VCARD
That card is 115 bytes long and makes a version 7 code at level M, which holds 122 bytes. Version 6 at M holds 106 bytes, so the card is 9 bytes too long for version 6, which is why it steps up to version 7. Shorter cards make smaller codes: a card with only a name, such as Madonna with no other fields, is 58 bytes and fits version 4 at M.
The N field holds the structured name as last name, then first name, separated by a semicolon, with three empty slots after them for the middle name, prefix, and suffix. The FN field holds the full name as it should be displayed. ORG, TEL, and EMAIL are optional: leave a field blank in the form and the tool leaves that line out of the card.
Semicolons and commas inside a value are escaped with a backslash, because those characters separate fields and list items in the format. A last name of Doe, Jr. is written as Doe\, Jr. and an organization of Smith; Sons as Smith\; Sons. A backslash in a value is doubled. The tool handles all of this for you; the Encoded text box shows the result so you can check it.
When someone scans a contact code, the phone should offer to add the contact to the address book. If it shows only text, the card is probably missing a required field or has a broken line: compare it with the example above and check that it begins with BEGIN:VCARD and ends with END:VCARD.
Common mistakes to avoid
- Printing too small. A dense code printed at postage-stamp size will not scan. Print a test copy at the real size and scan it with a phone at the distance a real person will stand. If it fails, print bigger or shorten the content.
- Cropping the white border. The quiet zone, four modules of white space around the code, is part of the symbol. Scanners use it to find the edges. The PNG download includes it; do not trim it off in an image editor.
- Weak contrast. QR codes need dark modules on a light background. Light gray on white, or a colored code on a busy photograph, fails in poor light. Black on white always works.
- Forgetting https:// on a link. Without the protocol, some camera apps show the address as plain text instead of offering to open it. Include the full address.
- Typing the Wi-Fi password from memory. One wrong character makes a code that joins nothing. Copy the password from the router settings page, and scan a test copy with a phone that is not already on the network.
- Using a photo of a screen as the print file. A screenshot of a code is a low-resolution image with screen glare and moire. Use the Download PNG button and print the file itself.
- Changing the password after printing. A Wi-Fi code is static: the password is inside the pattern. Change the password and every printed copy stops working. Plan the password before you print the sign.
- Stretching the code out of square. A QR code must stay square. Stretching it into a rectangle in a layout program distorts the module grid and breaks scanning. Resize by the corner handle, keeping the proportions locked.
- Putting a logo over the finder patterns. The three big squares in the corners are how a scanner finds and orients the code. Covering one of them, even partly, can make the code unreadable. If you must add a logo, keep it small, centered, and away from the corners, and use error correction level H so the covered modules can be rebuilt.
- Assuming every phone reads every format. Wi-Fi codes work on Android and on iPhone with iOS 11 and later, but behavior varies by maker and version, especially for hidden networks and WPA3. Test on both platforms before you print, and print the network name and password in text beside the code for anyone whose camera does not offer to join.
Frequently asked questions
Is this QR code generator really free?
Yes. There is no account, no sign-up, no watermark, and no limit on how many codes you make. The PNG download is free at all three sizes, and the code never expires, because the content is stored in the pattern itself rather than on a server.
Does this tool upload my text or Wi-Fi password anywhere?
No. The encoder runs entirely in your browser: your text, your Wi-Fi password, and your contact details are turned into a QR code on your own device and never leave the page. Nothing is sent to a server, nothing is stored in a cookie or a database, and closing the tab erases everything. That is the point of building the encoder into the page instead of calling an online service.
What is the largest amount of text a QR code can hold?
In byte mode, which is what this tool uses, the largest code (version 40 at error correction level L) holds 2,953 bytes of text. At level H the same version holds 1,273 bytes, because more of the space goes to error correction. A code holding only digits can fit 7,089 of them, but that needs numeric mode, which this tool does not use. If your text is too long for the largest code at the level you picked, the tool tells you the limit and you can shorten the text or pick a lower level.
Which error correction level should I pick?
Medium (15 percent) is the right default for most uses: menus, flyers, business cards, and codes shown on a screen. Pick Low (7 percent) when the text is long and the code will live on a clean screen, because it leaves the most room for data. Pick Quartile (25 percent) or High (30 percent) when the code will be printed outdoors, handled, folded, or stuck on packaging, because those levels rebuild more of the code after damage. Higher levels make denser codes, so do not pick High out of habit for a code that will never be touched.
Will my Wi-Fi QR code work on iPhone and Android?
The format comes from the ZXing barcode project, which labels it for Android and iOS 11 and later, and modern phones on both platforms offer to join the network when they scan it. Test the printed code on one iPhone and one Android phone before you print a batch, because behavior varies by maker and version, especially for hidden networks. For a WPA3 network, this tool writes T:WPA, which is the value ZXing lists; test that too, since the sources disagree about whether some phones want a different value.
Why does my QR code get denser when I type more?
QR codes come in 40 versions, from 21 by 21 modules up to 177 by 177, and the tool picks the smallest version that fits your text at the error correction level you chose. Each version adds 4 modules per side. Short text fits version 1 or 2, which looks sparse and scans easily. Longer text steps up through the versions, and each step packs more modules into the same square, so the pattern looks denser. Raising the error correction level has the same effect, because more of each version is spent on error correction codewords instead of your data.
Can I print the QR code on a flyer or a sign?
Yes. Download the PNG at the 2048-pixel size for print, keep the white border around the code, and keep the code square when you place it in your layout. Print a test copy at the real size and scan it from the distance a real person will stand: if it fails, print it bigger or shorten the content. Black modules on a white background scan best; pale colors and busy backgrounds cause failures in poor light.
Sources
Every figure on this page comes from one of the sources below, each opened and read while this tool was built. The encoder itself follows the algorithm of Project Nayuki's qrcodegen library and was verified against that library and against the npm qrcode package before publication. Browse all free tools on the Tools Elite homepage.
- Thonky, Data Encoding (QR Code Tutorial) — error correction levels and recovery percentages, the 40 versions and their sizes, mode and character count indicators, pad bytes 236 and 17. Accessed 20 November 2026.
- Thonky, Character Capacities by Version, Mode, and Error Correction — the byte-mode capacity table for versions 1 to 40 and the version 40 maximums (7,089 numeric, 4,296 alphanumeric, 2,953 byte, 1,817 kanji). Accessed 20 November 2026.
- ZXing project, Barcode Contents — the Wi-Fi network format (T, S, P, H fields), the escaping rules for five special characters, the double-quote rule for hex-like values, the URL guidance, and the vCard example. Accessed 20 November 2026.
- IETF, RFC 2426: vCard MIME Directory Profile — vCard 3.0, the required FN, N, and VERSION fields, and the VERSION value 3.0. Accessed 20 November 2026.
- Project Nayuki, QR Code generator library — the encoder algorithm this tool follows (MIT License), the 40 versions and four error correction levels of QR Code Model 2, automatic mask selection across all eight masks, and the four-module border. Accessed 20 November 2026.
- Summa, QR Code: History, How It Works, and Verified Facts — the 1994 Denso Wave origin, Masahiro Hara and the two-person team, the car-parts purpose, the Quick Response name, the unexercised patent, and ISO/IEC 18004 first published in 2000. Accessed 20 November 2026.