Create a static QR code for a fixed payload
''A static QR code stores its payload directly in the pattern of dark and light modules. This generator can encode text, a website URL or Wi-Fi connection details and export the result as a PNG image. It works locally in your browser. It does not create a hosted redirect, a scan dashboard or a destination that can be changed after printing through this toolkit.
Choose the payload type and enter the exact content first. Then choose dark and light colours, output width, margin and error correction level. The available width range is 128 to 2048 pixels, the margin range is 4 to 16 modules, and the error correction options are L, M, Q and H. These controls affect the image and its encoding trade-offs, but none can guarantee that every camera will scan every physical print.
For a URL payload, the QR code stores the address rather than a copy of the website. A scanner must still open that address through its normal network connection, and the destination must remain available. A text payload can be displayed without a web visit. Wi-Fi details are encoded for compatible scanners, whose support and connection prompts can vary by device.
Prepare text, URL or Wi-Fi content
''Text payload
Use text for a short message, reference or other information that should be carried directly by the code. Keep it concise enough to remain practical to scan. Long payloads require more modules and can become harder to reproduce at a small physical size. The tool's general text input limit does not mean a QR code can encode every possible input length; the QR encoder can reject a payload that exceeds its capacity.
Website URL
Use the complete destination you intend people to visit, preferably a stable HTTPS address where appropriate. Check spelling, path, query and any fragment before generating. The generator does not fetch or validate the destination. A code can be perfectly readable and still send people to the wrong page if the typed URL is wrong. Test the destination separately and then scan the generated code.
Wi-Fi connection details
Enter the network name and security details exactly as configured on the network. Case and punctuation can matter. A Wi-Fi QR code makes those details easier for someone to obtain; it does not hide the password. Place it only where sharing access is intended. Use an appropriate guest network if that matches your network policy, and remember that a password change makes an old printed code outdated.
Do not put private tokens or confidential information into a code just because the pattern is difficult to read by eye. A scanner can recover the payload. The code is a convenient representation, not encryption. Review what a person will learn from scanning it before displaying or distributing the PNG.
Choose image controls for a usable result
''Dark and light colours
Use a strong distinction between dark modules and the light background. Dark on a plain light background is a practical starting point. Low contrast, patterned backgrounds and unusual colour combinations can reduce reliability on some cameras. Judge the actual rendered and printed code, not only the colour swatches. Colour is a design choice that should be tested in the final setting.
Pixel width
The width control sets the raster PNG size between 128 and 2048 pixels. A larger export gives you more image detail for placement and print workflows, but it does not automatically determine the physical printed size. The same PNG can be printed very small or very large by another application. Avoid scaling it down so far that modules blur or merge, and test the size that readers will actually use.
Margin in modules
The margin is blank space around the code measured in modules, not a fixed number of image pixels. Keep that space clear when placing the PNG beside text, borders or photographs. Cropping it away can reduce scanning reliability. The available range is 4 to 16 modules, so choose a layout that can preserve the generated border rather than squeezing the code against nearby artwork.
Error correction level
L, M, Q and H provide different error correction choices. Higher correction can add redundancy but may also make the code denser for the same payload. It is not permission to cover modules with a logo or damage the print. Choose a setting, export it and test with the intended payload and physical size. This generator does not provide a logo-placement safety guarantee or a proof of scan performance.
A complete generate, export and test workflow
''First finalize the payload. For a campaign URL, build the UTM parameters before generating the QR code and test the complete tagged destination. For Wi-Fi, verify the exact network name and credentials. For text, read the final message for errors. Changing image colours after a scan test does not validate a later change to the payload, so keep the content version clear.
Generate a preview using conservative contrast and enough margin. Inspect it for a complete square pattern and an intact blank border. If the encoder rejects the data, shorten the payload where appropriate rather than repeatedly increasing the pixel width. More pixels do not increase the underlying encoding capacity. A shorter stable URL can be useful if you control a suitable destination or redirect infrastructure.
Download the PNG and place it into the actual document, sign or screen layout. Preserve its proportions and do not stretch one axis. Keep the margin visible and avoid overlays. If another editor resamples the image, inspect the exported result for blurred module edges. A correct browser preview is only one stage of the final asset.
Test the final asset with more than one relevant device when possible. Scan from the intended viewing distance and lighting, and test a printed proof if the code will be printed. Confirm not just that a scanner recognizes a code, but that the decoded payload and destination are correct. For Wi-Fi, confirm that a compatible device can use the details as intended.
Keep the payload and the final PNG together in your project records. Record where a printed code will be used and who maintains its destination. A static URL code can continue to work only while the address behaves as intended. There is no included service that updates all copies or alerts you when the destination changes.
Static limits and troubleshooting
''If scanning is unreliable, simplify the conditions before changing many controls at once. Try a dark code on a plain light background, preserve a generous clear margin, enlarge the physical placement and reduce the payload if possible. Check that the PNG was not stretched, heavily compressed or overlaid. Test the revised final asset again rather than assuming one change solved every cause.
If the scanner reads the code but the page fails, the QR pattern may be fine. Check the decoded URL, network connection, redirects and destination availability. The generator does not host the destination or verify it. A broken page, expired domain or access-controlled route is a separate problem from image readability.
If a Wi-Fi code does not connect, verify the network name, password and security selection against the router configuration. Device support can vary, and a scanner may show the details instead of initiating a connection. Do not assume every failure means the QR image is wrong. Test the credentials through a normal connection method as well.
After printing, the encoded payload cannot be edited in the ink. If it contains a URL, a server you control may change what that stable address serves or where it redirects, but that is separate infrastructure. This toolkit does not provide editable destinations. Plan printed materials around a stable address and maintain it for the intended lifespan of the asset.
The code has no built-in scan analytics here. A tagged URL can support destination visit reporting when analytics is correctly configured, but that is different from counting every scan. Do not report scan totals based only on generating a PNG. Choose measurement that matches the event you actually need to observe.
Practice: prepare a printed information card
Suppose you are making an information card with a website QR code. Start by choosing a destination you can maintain for the card's intended lifetime. Check that the page works without an unexpected account requirement and that its content matches the card. The static code stores the address you choose today. It does not create a management service that will repair a broken link or notify you when a domain or page changes.
Keep a payload record beside the design file. Include the exact URL, any campaign labels, the purpose of the card and the final PNG filename. If you later create several versions, this record helps distinguish them without trying to infer the destination from a black-and-white pattern. Use the same discipline for Wi-Fi cards, while storing credentials only in a place appropriate to the intended access policy.
Generate with clearly dark modules and a plain light background, then place the PNG into the design without stretching it. Preserve the clear margin even if the layout feels tight. A decorative frame should sit outside that margin rather than intruding into it. Avoid positioning the code over a photograph or fold where the pattern may be obscured. These choices improve the conditions for scanning but still require a real test.
Export the complete card and inspect that exported file. Another editor may resample the PNG, reduce its resolution or apply image effects. A crisp preview in the generator does not prove the design export retained crisp modules. If the card will be printed, use a physical proof at the intended size and material. Gloss, low contrast, folds and lighting can affect what a camera actually sees.
Scan the proof from the distance at which a person is likely to use it. Try relevant devices and ordinary lighting rather than testing only one phone at a perfect angle. Read the decoded address before opening and verify the complete destination journey. A successful recognition beep is only the first step; it does not prove the page is correct, accessible or maintained.
Before ordering or distributing many copies, freeze the reviewed payload and final artwork together. If the destination changes later, decide whether your own server can maintain the original address or whether a new print is needed. This toolkit cannot update ink or provide scan analytics. A good maintenance plan is therefore part of a useful static QR asset, along with a readable pattern and an accurate destination.
For a displayed Wi-Fi code, plan what happens when network credentials change. The old print continues to reveal the old payload even if it no longer connects. Replace or remove outdated copies through your normal access-management process and generate a new image from the approved details. The generator does not discover old prints or revoke network access. Keeping a simple inventory of where the code is displayed can make that maintenance task manageable without pretending that the static image is an access-control system.
Local processing and a reliable review
This tool carries out its operation in your browser. It does not send the values you enter to a remote processing service, and it does not need an account to produce a result. The page still runs within your device and browser environment: anyone with access to your screen, an exported file, or a copied clipboard value may be able to read that material. Choose input that you are allowed to handle on the device you are using.
Text fields have the general one-hundred-thousand-character input boundary, but QR encoding capacity imposes a much smaller practical limit on a single payload. A long message can be rejected even when it fits in the text field. Export width affects the PNG pixels rather than increasing that capacity. If generation fails, inspect the payload and shorten it where appropriate. Browser memory can also affect responsiveness. Test a representative code before preparing a large design, and test the exact final printed or displayed version after all placement and export steps are complete.
Keep your source separately until you have checked the output. A browser result can be useful and still be unsuitable for the final place where you intend to use it. The receiving form may have different limits, a house style may need a manual edit, or a document may require facts that no mechanical conversion can infer. Compare one simple case by hand, then inspect a case near the boundary that matters to your work.
Treat the QR image and its destination as two things to maintain. Test the exact final asset, protect the encoded information, and plan for the fact that printed static data cannot be edited by this generator.
Frequently asked questions
What makes this a static QR code?
Its payload is encoded directly into the pattern. The printed or saved image continues to contain that same data. This toolkit does not insert a managed redirect service that lets you change the payload later. If the payload is a URL under your control, you may maintain that server separately, but the code itself still stores the original URL.
Can I change the destination after printing?
You cannot change the encoded text in an existing print. A stable URL on a server you control can redirect or serve different content, but that server functionality is not included here. Plan the destination before printing and keep it maintained. Creating a new QR image does not update copies already distributed.
Does the generator track scans?
No. It creates a static image without a scan analytics service. A destination website may record visits if it has proper analytics, and a UTM-tagged URL can carry campaign labels. Those visits are not automatically the same as scan counts. Define the event you need to measure and configure that measurement separately.
What payload types are supported?
You can generate a code for text, a website URL or Wi-Fi connection details. Each type has a different use: text is carried directly, a URL points elsewhere, and Wi-Fi details depend on compatible device support. Review the exact payload before generating because the code cannot infer the intended message or correct a mistyped address.
What image size can I export?
The width range is 128 to 2048 pixels, with PNG export. Pixel width is separate from physical print size. A layout program can scale the same image to many sizes, so test the actual placement. More pixels do not increase QR payload capacity or guarantee that a very small physical code will scan.
What does the margin setting mean?
The margin is clear space around the QR pattern, measured in modules. The available range is 4 to 16 modules. Preserve that border in the final layout and keep nearby text or artwork outside it. Cropping the blank area or placing the code against a busy background can make recognition less reliable.
Which error correction level should I choose?
L, M, Q and H offer different redundancy choices. Higher correction can increase density, so the best practical choice depends on payload and final size. Test the result in its real setting. Error correction is not a guarantee that a covered, blurred or damaged code will work, and it does not authorize placing a logo over the pattern.
Can I use brand colours?
Yes, with the dark and light colour controls, but keep strong contrast and test the final output. A design that looks attractive on one screen can scan poorly on another camera or in print. Start with a plain light background and clearly dark modules. Verify the actual asset under the intended viewing conditions.
Why does a long URL make a dense code?
More payload data generally needs more modules. A dense code can be harder to reproduce at a small physical size. Increasing export pixels helps raster detail but does not remove the underlying density. Consider a shorter stable address under your control if your infrastructure supports it, and test the final printed or displayed size.
Can the code contain a private password?
A QR pattern is not encryption. Anyone who can scan it may recover the payload. Wi-Fi codes intentionally share connection details, so display them only where that access is intended. Do not put unrelated secrets or private tokens into a code merely because the pattern is unreadable to the naked eye.
Will a URL code work without internet?
The scanner can decode the stored URL without fetching the page, but opening the destination normally needs a working network connection and an available server. A text payload can be read directly without a web visit. This generator does not cache the website inside the code or provide offline copies of destination content.
Why can my phone read the code but not connect to Wi-Fi?
Check the network name, password and security details against the actual network configuration. Compatible scanner behavior varies, and a device may display details rather than join automatically. Test the credentials using a normal connection flow too. A successful scan proves the payload was read, not that the network will accept it.
Can I add a logo over the QR code?
This toolkit does not provide a safe logo-overlay workflow or guarantee. Covering modules can make the code fail even with error correction. Keep the generated pattern intact for a conservative result. If you use another design process, test the final image and print carefully rather than assuming redundancy will compensate for an overlay.
Why did the code fail after I placed it in a document?
The layout process may have stretched, downscaled, blurred, cropped or covered part of the PNG. Inspect the final exported document, preserve the clear margin and test a printed proof if relevant. The browser preview and the final asset are separate stages. A scan test should use the actual version readers will receive.
Is there a guaranteed minimum print size?
No universal physical size is promised here. Payload density, printer quality, camera, distance, lighting and surrounding layout all affect scanning. Use a sensible placement and test it under realistic conditions. Do not infer a guaranteed print size from the pixel width alone, because another application controls how large that image appears on paper.
What should I verify before distributing a code?
Scan the final asset, inspect the decoded payload and complete the intended action. Check the destination page or Wi-Fi connection, preserve the margin and test relevant devices and lighting. Keep the final payload and PNG together for maintenance. For printed URLs, confirm who will keep the destination working over time.
Useful next steps
Choose a related tool when its operation matches the next part of your task. Check the result at each stage so a small source mistake does not carry into the final output.