QR Code Generator Guide: Static Links, Byte Limits and Clear Exports
Admin ·
QR code generator turns the current text or link into a static QR image in your browser. The preview updates when you edit the input or correction level. Download a black-on-white PNG with whole-pixel modules or a scalable SVG, both with a four-module clear border.
The image contains a fixed payload, while a linked destination can change or fail externally. Input units and UTF-8 byte capacity differ, and PNG size choices are targets. Error correction and a successful preview do not guarantee scan distance, destination safety or identical interpretation on every reader.
Create a code with the live preview
QR code generator begins with an empty Text or link field, Medium error correction and a PNG size target of 1024 pixels. Type or paste your payload and the preview appears automatically. Editing the text or choosing another error correction level recalculates the symbol; there is no separate Generate button.
Read the current text before downloading. If it is a link, check the full intended address independently, including its scheme, path and query. The preview confirms that the text fits this encoder at the chosen level; it does not establish that a website exists, that its content is safe or that a phone will open it successfully.
- Enter the text or link you want the code to contain.
- Choose error correction and, for PNG, the target size; check the preview and any error.
- Download the intended format and test the actual file or printed copy with the intended reader.
The payload is text, rather than a verified destination
The encoder uses the current textarea value without trimming it, shortening a URL or fetching its destination. Spaces, line breaks, case and punctuation can therefore matter. A missing scheme or an unintended trailing character remains part of the input. The workspace does not turn every string into a valid web address.
A reader decides how to present or act on decoded text. The same generic encoder can hold ordinary text or an already formatted payload, but this workspace supplies no guided Wi-Fi, contact-card, payment or email builder. A successful preview is not validation of one of those external formats.
Static bytes and changing linked content are different
A downloaded QR image contains a fixed encoded payload. Changing that payload requires generating a new image. ToolMellow inserts no intermediate scan redirect, expiration timer or editable destination dashboard. A historical phrase such as Permanent QR code generator describes that static format, rather than a promise about the lifetime of an external service.
An unchanged address such as https://example.com/menu can serve different content later, or its owner can change a redirect behind it. The URL can also stop working, require authentication or become inaccessible to a reader. Choose an address you can maintain and retest it after changes; the QR image itself cannot keep a destination online.
Visible characters, input units and encoded bytes differ
The textarea limits user input to 3000 UTF-16 code units. The encoder separately turns a well-formed JavaScript string into UTF-8 bytes. A visible character does not have one universal cost: a uses one UTF-8 byte, é uses two, 世 uses three and 😀 uses four. The emoji also uses two UTF-16 code units.
Consequently, text can pass the textarea limit yet exceed the selected QR byte capacity. The encoder rejects unpaired Unicode surrogates rather than silently replacing them. Shortening the payload is preferable to assuming a visible-character count measures its byte length. These limits apply to the text in the field, rather than to an uploaded file, because this workspace has no file-input workflow.
MDN: TextEncoder and UTF-8 bytesMDN: maxlength and UTF-16 input unitsMDN: detecting unpaired Unicode surrogates
Capacity is finite and depends on the selected level
This implementation always uses a single UTF-8 byte-mode segment. It does not optimize digits into numeric mode, use an alphanumeric or Kanji segment, or emit an ECI segment. General QR capacity figures for other modes therefore do not describe this tool. The table lists this encoder’s maximum byte payloads at version 40; smaller versions hold less.
The default is M, so 2953 bytes is not the default limit. For example, 世 repeated 984 times uses 2952 bytes and fits at L, while 985 repetitions use 2955 bytes and exceed its ceiling. Choosing another level can change both the fitting capacity and the chosen version; the textarea’s separate input limit still applies.
| Level | Maximum UTF-8 bytes at version 40 | Meaning of the control choice |
|---|---|---|
L | 2953 | Low error correction |
M | 2331 | Medium; workspace default |
Q | 1663 | Quartile error correction |
H | 1273 | High error correction |
DENSO WAVE: QR versions and capacityMDN: TextEncoder and UTF-8 bytes
Version and module count explain the symbol’s density
The encoder chooses the smallest fitting ordinary QR version from 1 to 40 for the payload and selected level. The side length is 17 + 4 * version modules: version 1 has 21 modules per side, and version 40 has 177. The displayed version and module count describe the symbol before its clear border.
Adding bytes or changing correction may increase the selected version, but a change does not always cross a capacity boundary. If the version remains the same, the number of modules per side remains the same even when their pattern changes. At a fixed physical size, more modules generally mean smaller individual squares; the preview alone does not measure a reliable reading distance.
DENSO WAVE: QR versions and capacityDENSO WAVE: clear margins and module dimensions
Recovery labels are not permission to cover image area
The controls label L, M, Q and H with about 7%, 15%, 25% and 30% recovery. DENSO WAVE explains error-correction restoration in terms of total codewords, with each codeword containing eight bits. These labels do not identify percentages of the visible image that you can safely obscure, erase or replace with a logo.
Recovery depends on which information is damaged and on whether the reader can locate and interpret the symbol. A higher level may require a larger version for the same payload, while a lower level does not guarantee longer scan distance. Keep the finder patterns and clear border intact, and test the intended output. This tool does not test damaged symbols or certify a logo overlay.
DENSO WAVE: error correction and codeword restorationDENSO WAVE: clear margins and module dimensions
PNG choices are targets, so the downloaded side can be smaller
PNG size offers targets of 256, 512, 1024 and 2048 pixels. The renderer includes a four-module border on every side and assigns a whole number of pixels to each module. Its square side is (size + 8) * floor(target / (size + 8)) for these choices. It paints black squares on opaque white, rather than stretching fractional module edges to fill an exact target.
For a version 1 symbol, the full extent is 29 modules: 21 for the symbol plus eight for both margins. The examples below therefore apply to a short payload such as a at M. A version 40 symbol has a 185-module full extent, so a 1024 target produces 925 pixels. PNG size does not increase payload capacity or change the encoded bytes.
| PNG target, version 1 | Whole pixels per module | Exported square side |
|---|---|---|
256 | 8 | 232 pixels |
512 | 17 | 493 pixels |
1024 | 35 | 1015 pixels |
2048 | 70 | 2030 pixels |
DENSO WAVE: clear margins and module dimensionsMDN: Canvas.toBlob, PNG export and null results
SVG keeps vector geometry and the four-module quiet zone
Download SVG produces a fixed black-on-white vector symbol with a viewBox covering the code and its four-module clear border. The file has no fixed pixel width or height. Scaling it in a layout changes its displayed or printed dimensions while retaining its vector geometry; the PNG size selector does not set an SVG export size.
Preserve the surrounding white margin when placing the code in a document. Cropping the border, overlapping artwork or putting similar dark marks beside the symbol can make reading harder. Vector format does not guarantee that an arbitrarily small print, a blurred screenshot or every reader will decode it. Choose the full placed size and test the exported or printed result.
Input errors replace the preview, and Clear retains choices
When text exceeds capacity or contains malformed Unicode, an error replaces the preview and download actions. The field keeps its current text; the app does not truncate it into a different valid payload or continue offering an old image. Shortening the text or changing the correction level recalculates the result. Changing PNG size alone does not resolve a byte-capacity error.
Clear is available with a valid preview. It empties the text, removes the current code and shows the cleared notice while keeping the correction level and PNG target. Text edits clear notices; level and size changes do not explicitly clear them. To empty an invalid field, edit or delete its text. Reloading restores empty input, M and target 1024.
MDN: detecting unpaired Unicode surrogatesMDN: maxlength and UTF-16 input units
Local generation does not encrypt a QR payload
The component computes the QR symbol and creates export data in the browser without a generation request carrying the entered text. There is no ToolMellow scan redirect or scan-analytics dashboard added to the code. Ordinary website hosting and analytics, and any requests made when someone follows the encoded destination, are separate from this local generation step.
A QR image is a representation of data that a reader may reveal. Downloading, printing or sharing it creates copies outside this workspace, and a link inside it can lead to a service with its own tracking or access rules. Error correction improves resilience to some corruption; it is not encryption, authentication or protection against someone reading the payload.
Downloads are external copies, with PNG and SVG alternatives
The two export filenames are toolmellow-qr-code.png and toolmellow-qr-code.svg. PNG is drawn through a local canvas, while SVG is built from the current module geometry. If the browser cannot obtain the canvas drawing context, the workspace displays a notice recommending SVG. If PNG conversion returns no Blob, it produces no downloaded file and no new failure notice.
If no file appears, try SVG and check the browser’s download handling. The shared download helper revokes its temporary object URL after 60 seconds; that releases the browser URL rather than deleting a saved image. Clear and reload do not erase already downloaded files or copies that you placed in another document.
MDN: Canvas.toBlob, PNG export and null resultsMDN: File API, Blob objects and object URLsW3C File API: revoking an object URL
Test the actual output under the intended conditions
Check the decoded payload, not merely whether a reader detects a square. For links, verify the address and destination on the intended device and network. For text containing several scripts or emoji, check the decoded text as well: this encoder writes UTF-8 byte mode without an ECI marker, so the interpretation chosen by a reader should be tested.
Use the actual file at its final placed size. Preserve contrast and the quiet zone, avoid blur and unwanted resampling, and test a printed proof if you will distribute print copies. Dense symbols, small modules, lighting, reflections, damage and the reader can affect results. No particular PNG target, correction level or vector export establishes a universal physical size or scan distance.
DENSO WAVE: clear margins and module dimensionsDENSO WAVE: error correction and codeword restorationMDN: TextEncoder and UTF-8 bytes
Know which workflow this workspace provides
This is a one-payload static text encoder with correction-level and PNG-target controls. It provides PNG and SVG downloads. The workspace has no bulk generation, image scanner, custom colors, logo editor, URL shortener, editable dynamic redirect, scan statistics, account history or hosted file-upload service.
Library helpers can accept additional parameters that the page does not expose; those parameters are not workspace features. An already formatted text payload may be encodable, but there is no dedicated builder or validator for Wi-Fi credentials, contact cards or payment instructions. Use a workflow that validates the needed format, then test its decoded result instead of assuming any preview verifies its semantics.
Troubleshoot the layer that failed
A missing preview, an unexpectedly small PNG, a reader’s decoding error and a dead linked page are different failures. Start with the visible text, chosen level and current error. Then inspect the exported file and its placement, followed by the actual reader and destination. Changing an unrelated control will not fix every layer.
The table connects common symptoms to checks you can make in this workspace. It is a decision aid, rather than a promise that each device, browser or printed sample will work. Keep a copy of the intended payload so that you can compare what the reader actually decodes.
| Symptom | Likely layer to check | Useful next action |
|---|---|---|
| Text-too-long error | UTF-8 byte capacity at selected level | Shorten the payload or choose another suitable level; PNG target is unrelated. |
| PNG smaller than selected target | Whole-module raster geometry | Use the actual exported dimensions; choose a larger target or SVG if useful. |
| Reader cannot decode or shows wrong text | Placement, symbol/reader interpretation | Keep the border, enlarge appropriately and test the original file and intended payload. |
| Reader detects a code but the page fails | External destination or access | Check the decoded URL, availability, redirects, authentication and network. |
DENSO WAVE: clear margins and module dimensionsDENSO WAVE: error correction and codeword restoration
Use related tools without changing the payload by accident
URL encoder and decoder can help inspect an encoded component, but blindly encoding an entire address or encoding it twice can change its meaning. Text cleaner can deliberately remove unwanted characters before you paste a payload; review those edits because this QR workspace itself does not trim or normalize the text for you.
Image resizer may help prepare a PNG for a layout, but resampling changes its pixels and can soften module edges. Preserve the quiet zone and recheck the result. For a vector layout, keep the original SVG geometry and choose an appropriate placed size. These are separate tool workflows; the QR page does not automatically upload or hand off its payload to them.
Common questions
Do these codes expire?
ToolMellow adds no expiration timer to the static image. Its encoded payload remains fixed, while an external URL can stop working, require access or lead to content that changes. Permanent/static wording does not guarantee destination lifetime.
Can I change a destination without reprinting the code?
Changing the encoded URL requires a new image. If you control the unchanged URL, you may change its served content or redirects externally. This workspace supplies no hosted dynamic-code management service.
Does the preview check whether a URL works?
No. It encodes the current text when it fits the selected level. It neither fetches the address nor validates its safety, availability or external payload format. Check the decoded address and destination independently.
How much text fits?
At version 40, byte-mode UTF-8 ceilings are 2953 at L, 2331 at M, 1663 at Q and 1273 at H. The default is M. The textarea also limits user input to 3000 UTF-16 code units; neither limit is a universal visible-character count.
What happens to spaces, line breaks and Unicode?
The encoder uses the current textarea value without trimming it. It writes well-formed text as UTF-8 bytes, rejects unpaired surrogates and emits no ECI segment. Test non-ASCII decoded text on the intended reader rather than assuming universal interpretation.
Does higher error correction always make a denser code?
No. A selected level can require a larger fitting version for the same bytes, but module count changes only if the version changes. The controls’ approximate recovery labels describe an error-correction topic, rather than guaranteed scan distance.
Can I cover 30% of the code with a logo?
The 30% value is an approximate recovery label on the H control, not a safe proportion of image area to cover. DENSO WAVE discusses recovery in codewords; damage placement and detection matter. This workspace has no logo tool or overlay verification.
Why is a 1024-pixel choice not an exact 1024-pixel export?
The renderer keeps integer pixels per module and includes the clear border. A version 1 symbol has 29 modules across its full extent, so target 1024 yields 1015 pixels. Other versions produce different rounded dimensions.
Does the PNG size selector change the SVG?
No. It affects future PNG raster exports. SVG has scalable viewBox geometry and the four-module clear border; no fixed exported pixel width is selected for SVG.
What does Clear remove?
With a valid preview, Clear empties the text and removes that preview while retaining correction and PNG-target choices. It does not erase exported files. When input is invalid and download/Clear actions are absent, edit or delete the text directly.
Why did PNG not download?
A missing canvas context displays a notice offering SVG. A null PNG Blob produces no file and no new notice. Try SVG and check browser download handling; this guide does not establish compatibility with every browser.
Are my text and scans sent to ToolMellow?
Generation runs in the browser without a request containing the entered payload, and no ToolMellow scan redirect is inserted. General site hosting/analytics and requests to a destination when someone follows it are separate. A shared QR image itself can reveal its payload.
Can this create dynamic codes, add logos or process a batch?
Those workspace features are absent. It provides one static text payload, correction choice, a PNG target and PNG/SVG downloads. Generic formatted text does not imply dedicated Wi-Fi, contact or payment validation.
What should I test before distributing a code?
Test the actual exported or printed copy at its intended size with representative readers. Check decoded text, the complete URL and destination access, preserve the clear border and contrast, and retest after resampling or external destination changes.
Sources and further reading
- DENSO WAVE: QR versions and capacity
- DENSO WAVE: error correction and codeword restoration
- DENSO WAVE: clear margins and module dimensions
- MDN: TextEncoder and UTF-8 bytes
- MDN: maxlength and UTF-16 input units
- MDN: detecting unpaired Unicode surrogates
- MDN: Canvas.toBlob, PNG export and null results
- MDN: File API, Blob objects and object URLs
- W3C File API: revoking an object URL