How to Generate a QR Code from a Website
Create a QR code for any webpage in Chrome, Edge, or Firefox, verify the URL, download it, and avoid common scanning problems.
You can turn any webpage into a QR code without installing a dedicated app. Open the exact page in Chrome or Edge, use the browser’s built-in QR-code command, download the image, and scan-test it before sharing or printing. Firefox Desktop can also create the code locally.
Generate a QR code in Google Chrome
- Open the exact webpage you want people to visit.
- Check the address bar. Confirm the page, spelling, path, and
https://scheme are correct. - Select More (the three-dot menu), then Cast, save, and share, and choose Create QR code.
- Copy the QR link, download the code, or scan it with another device.
Chrome generates a code for the page currently open. If you need a different page, navigate there first and repeat the steps. Google documents this workflow in Chrome Help.
Generate a QR code in Microsoft Edge
- Open the webpage.
- Right-click an empty area of the page.
- Select Create QR code for this page.
- Share the link or download the QR code as a PNG.
Edge’s built-in generator is documented by Microsoft Support. Availability can vary by browser version, device, and market. Microsoft’s policy entry lists support for Windows 125+, macOS 125+, and Android 140+, while iOS is marked unsupported in that entry.
Generate one in Firefox Desktop
Firefox Desktop offers local QR-code generation. Mozilla says the URL is not uploaded or stored during generation, which is useful when you want the address to remain on your computer. Open the page, use Firefox’s page-sharing or QR-code command when available, then save the generated image. Check Mozilla Support for the current menu location in your Firefox version.
Download and test the QR image
- Save the PNG using the browser’s download control.
- Open the saved file and confirm it is complete and not clipped.
- Scan it with a phone camera or QR scanner.
- Confirm that the scan opens the intended page over HTTPS.
- If printing, keep the code unobstructed and preserve strong contrast.
Testing the final file catches a wrong URL, a damaged export, or a code that is too small or low-contrast for the intended scanner.
Static versus dynamic QR codes
A browser-generated QR code normally stores the destination URL directly. That makes it static: after you distribute or print the image, changing the destination requires generating and distributing a new code.
A dynamic QR service stores a hosted redirect or identifier in the code. You can usually change the destination later and may receive scan analytics, but every scan depends on that service and its redirect domain. Aalto University warns that dynamic codes can be redirected to a malicious website, so verify both the redirect domain and final destination before publishing.
| Choose | Best for | Trade-off |
|---|---|---|
| Static browser code | A stable page, simple sharing, or a one-time print run | The URL cannot be edited after distribution |
| Dynamic service | Post-print destination changes or scan measurement | Introduces a hosted redirect and service dependency |
URL checks before you create the code
- Open the exact page, rather than the site homepage, if the QR code should deep-link to an article, product, form, or checkout.
- Check spelling, capitalization, query parameters, and fragment identifiers.
- Remove temporary preview or admin parameters before publishing.
- Prefer the HTTPS version when the site supports it.
- Scan the exported image, not only the browser preview.
Aalto University’s QR guidance specifically recommends checking and correcting the link before generation.
Or skip the browser setup
If you need a clean image of the webpage to use alongside a QR code, ScreenshotNeo captures it with one request. It accepts cookie and consent banners, removes more than 60 known consent platforms plus newsletter popups and chat widgets, and lets each cleanup step be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed; the response identifies the result with X-Page-Verdict and X-Billed headers. The QR code itself still encodes your URL, so generate it in Chrome, Edge, or Firefox after confirming the address.
See the ScreenshotNeo API documentation for all options.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);The service also provides an MCP server with take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. One thousand screenshots per month are free with no card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.
Troubleshooting
| Problem | Likely cause | Fix |
|---|---|---|
| The QR command is missing | Browser version, device, policy, or market does not support it | Update the browser, try Chrome or Firefox Desktop, or use a reputable QR generator. |
| The scan opens the wrong page | The wrong tab or URL was used | Return to the intended page, verify the address bar, regenerate, and rescan. |
| The image will not scan | Clipping, low contrast, obstruction, or an overly small print | Download again, preserve the complete square, keep strong contrast, enlarge the print, and test under the expected lighting. |
| The page requires a login | The QR code only stores the URL; it cannot provide authentication | Use a publicly reachable landing page or ensure recipients can sign in. |
| The destination changed after printing | Static codes contain a fixed URL | Generate and redistribute a new code, or plan a trusted dynamic redirect before printing. |
| A ScreenshotNeo capture is blank or blocked | The target page failed to load, timed out, or presented a bot check | Inspect X-Page-Verdict and X-Billed, then adjust wait, headers, cookies, user agent, or blocking options in the API documentation. |
Performance, reliability, and cost
- Browser QR generation is local and normally immediate; it does not require a QR subscription.
- Static codes avoid a redirect service at scan time, which removes one dependency.
- Dynamic codes add flexibility and analytics but require the redirect service to remain available and trustworthy.
- For repeated webpage captures, ScreenshotNeo supports caching with a TTL you choose, async jobs with signed webhooks, bulk capture of up to 100 URLs per call, and a usage API. Only clean shots are billed; cache hits and failed captures are not.
- Keep a copy of every published QR image and record the destination URL used to create it.
FAQ
Can I create a QR code without an app?
Yes. Chrome and Edge include browser commands, and Firefox Desktop can generate one locally.
Does a QR code contain the webpage itself?
No. It normally contains the destination URL. The phone still needs network access to open the page.
Can I edit a Chrome-generated QR code later?
No. It is normally static. Create a new code, or use a trusted dynamic redirect when editing or analytics justify the added dependency.
Should I print the QR code immediately?
Scan-test the final downloaded image first, then test a physical proof if the code will be printed at production scale.
