One scan, straight to your page
You have a Facebook page that people like well enough once they find it, and a window, a flyer or a stand where nobody is going to type facebook.com and then your name into a phone. A printed square closes that gap. Paste the address below, set the colours, and take the file to the printer.
Tip: Ctrl+C or “Right click\Copy”
Displaying the logo on the QR code may take some time. Just wait for it to load.
When some colors are combined on the QR code, it may not work correctly. Don’t
forget to check before posting!
This is a link code. The pattern encodes one web address and nothing else, so scanning it does the same job as typing that address into a browser. Point a phone at the code and the camera shows the link as a banner; tap the banner and the page opens. On a phone with the Facebook app installed the link usually hands over to the app, which is what you want, because a reader who is already signed in can follow or comment without a second step. On a phone without the app, the mobile site loads in the browser instead. Nothing about the person scanning comes back to you, and the code carries no login of its own.
A code earns its space wherever the page holds something a flat sheet of paper cannot. The same reasoning applies to an Instagram profile, but Facebook is usually the one with the opening hours and the event dates on it.
Leave the margin alone. The quiet zone is four modules wide on every side, and a layout that crops to the edge of the pattern is the most common reason a printed code does nothing at all. Size follows reading distance: divide the distance by ten. A code on a table card read at 30 cm can be 3 cm across. A code in a first floor window read from the pavement two metres away needs about 20 cm. Keep it dark on a light background; inverted codes, light on dark, fail on a fair number of older readers even though a recent iPhone copes. If you drop a logo into the middle, keep error correction at Q or raise it to H so the reader can rebuild what the logo covers. And be clear about the limits. Once the code is printed the address is fixed, there is no scan counter, and no code has ever made anyone press Follow.
You can encode a page, a group, an event or a single post, and that choice matters more than the colours. Use the short vanity form, facebook.com/yourpage, whenever the page has one. The long address sitting in the browser bar after you have clicked around carries numeric ids and a tail of query parameters, and those are the parts that rot. An event id is dead weight the week after the event. A post permalink breaks if the post is deleted. A group id tells a reader nothing when the link banner flashes up before they tap.
Then check what a stranger sees. A private group shows a join screen to anyone who is not signed in, and some post permalinks show a login wall instead of the post. Open the address in a private browsing window before anything goes to print, and scan the finished code with a phone that is signed out. If the link only works for you, it will not work on a flyer. For a destination you may want to redirect later, build it on the editable code page instead, and the rest of the print checks are collected in 10 things to know before printing QR codes.
It is free, there is no account to create and no email to hand over. The file has no watermark, no expiry date and no scan limit. The image belongs to you once it is downloaded, and it keeps working for as long as the Facebook address inside it keeps working.
Not with a code made here on this page. A static code holds the address inside the pattern, so changing the destination means generating a new code and reprinting. If you expect the destination to move, make the code on the editable code page instead, where it points at a free-qr.com link you can repoint later.
That is decided by the phone, not by the code. If the app is installed, most phones hand a facebook.com link straight to it. If it is not installed, the mobile site opens in the browser. Either way the reader lands on the same page, though the app version is easier to follow from.
You can encode the address, but a person who is not a member sees a join or login screen rather than the posts, and someone with no Facebook account sees very little. That is acceptable if the point of the code is recruiting members. It is a poor choice if the code is meant to show information.
Divide the reading distance by ten. Read from half a metre, print about 5 cm. Read from three metres across a hall, print about 30 cm. Below roughly 2 cm nothing reliable happens at arm's length, and a code with a logo in it wants a little more room than one without.
No. A static code sends nothing back, so there is no count of scans and no country breakdown. Page insights on Facebook will show visits, but they cannot separate the ones that arrived from your printed code. Counting scans is only possible with an editable code.
