Office WiFi QR codes: one code per network, staff and guests kept apart
An office is not a café with one friendly password. It has a staff network, a guest network, a meeting-room network, and a row of devices nobody thinks about — and each one wants its own sign in its own place.
Office WiFi code
Download formats: PNG (1024 px, ready to print) and SVG (vector, scales for a print shop).
Something wrong?Report it— opens your mail app with the page path and browser details pre-filled. Nothing you typed into the generator is included.
- In your browser
- Never uploaded
- No account
Before you print
- Scan it first — open the exported PNG on your phone and check it reads before sending anything to a printer.
- Keep the white margin — the quiet zone around the code is what a camera needs to lock on. Cropping it is the most common reason a printed code fails.
- Dark on light reads best — inverted colors look stylish on screen but older phone cameras struggle with them on paper.
Print size at a glance
- 2 cmSticker, business card, table tent
- 4 cmFlyer, menu insert, small poster
- 8 cmWall sign, door plate
PNG exports at 1024×1024 and already includes the white margin around the code.
How big should you print it?
An office is not a café: what changes
In a café, one code on one wall covers the whole business, because the audience never changes: strangers come in, strangers leave, nobody expects to be on that network again tomorrow. An office breaks all three of those assumptions. Several networks run at once. The same people scan every day. And the people scanning are not only guests with phones — they are staff handsets, tablets at a reception desk, and a printer that has been on the same shelf since 2019.
So the unit of work here is not "a WiFi code." It is a small set of codes that each do one job, posted where that job happens. Get that map right and the signs follow in an afternoon.
Decide the network plan before you generate anything
Four decisions, all made before the first code is drawn. Skipping them is how offices end up with a single code taped to a wall and a password that cannot be changed without a reprint run.
How many networks exist, and what is each one for. Write the list out the way you would explain it to a new starter. If two networks turn out to serve the same purpose, merge them now — a code is cheap, but a sign that contradicts the other sign is not.
Who scans each one. Not "everyone." Staff on company handsets, staff on their own phones, visitors who sit in reception for twenty minutes, contractors who stay a week, devices with no person attached. Two of those groups sharing a password is fine; the contractor and the staff group sharing one is the mistake that shows up months later.
Who owns the password. One named person, ideally with a second. If the answer is "whoever set up the router in 2021," the rotation section below will not happen at all.
How often each will change. Pick the interval now, in plain terms — quarterly for staff, monthly for guests, on each contract start for contractors. The interval decides how many signs you print and where you print them, which is the next section.
Staff code and guest code: two files, two places, two rules
These two are the pair that matters, and they fail in opposite directions. The staff code has to be reachable by people who work here and effectively invisible to everyone else, which usually means it lives inside the building rather than at the entrance. The guest code has to be findable by someone who has never been here, which means it belongs in the open — reception, the meeting room, the wall next to the coffee machine.
Two rules follow. First, do not post the staff code where a visitor can photograph it from a waiting chair; the only protection a printed code has is where it hangs, becausethe password inside it is not hidden by being inside it. Second, when the guest password changes, nothing about the staff code should have to change — and that only holds if they were separate networks with separate passwords from day one.
Practically: name the files on your own machine before you print them, and put the network name in the sign text as well as in the code. A phone camera that refuses to focus on the code is a five-second problem when the network name is readable; it is a support ticket when it is not.
The multi-SSID plan: one code per network
The table below is the plan, not a suggestion. Each row is one code you generate and one sign you print. The last column is the part that matters: it says what you lose by collapsing that row into the staff code, which is what every office does before the first contractor leaves.
On a phone this table scrolls sideways.
| Network / SSID to type | Who scans it | Codes to print | Sign line (exact text) | Generator settings | Rotation | What goes wrong if it shares the staff code |
|---|---|---|---|---|---|---|
Corp-Staff | Employees, on both company handsets and their own phones | One per floor plate, plus one inside each meeting room | Staff WiFi — scan to join | WPA · Label: STAFF | Every 90 days, or the day someone leaves | — it is the staff code |
Corp-Guest | Visitors, interview candidates, contractors | One per reception desk, one per meeting room | Guest WiFi — scan to join | WPA · Label: GUEST | Monthly, or after any large event | A guest password change forces a reprint of every staff card as well |
Corp-Meeting | Anyone booked into that room | One per room, mounted inside the door | Meeting room WiFi | WPA · Label: room name | Quarterly | The room's password can only change when the whole office does |
Corp-Devices | Printers, displays, badge readers, handheld scanners | One per device cluster, filed — not posted | Do not post — devices only | WPA · hidden if needed · Label: DEVICES | Only when a device is reprovisioned | Device credentials end up on a sign anyone can photograph |
Corp-Floor2 | Shop-floor or second-floor staff and their tablets | One per floor, one at each stairwell exit | Floor 2 WiFi — scan to join | WPA · Label: FLOOR2 | Same schedule as staff | Floor and office passwords can never diverge |
Corp-Temp | Event crews, seasonal staff, contractors | One per worksite, collected when the job ends | Contractor WiFi — hand back the card | WPA · Label: TEMP | Each contract start | You cannot revoke a contractor without changing the staff password |
Generating one code per SSID, in order
The generator on this page makes one code at a time, so work down the table row by row. Do it in one sitting with the network list open: four values per network, and the fourth one — the label — is what stops you from ending up with six files called wifi-code.png.
Type the network name exactly as the router spells it
Case and spaces both count. Corp-Staff is not corpstaff. If two networks differ by one character, you will find out on someone else's phone at the worst possible moment.
Paste the password, then set the security type
WPA2 and WPA3 are both entered as WPA. Getting this wrong is the single most common reason a code scans and then fails to connect — the phone reads it, tries the wrong handshake, and quietly gives up.
Tick hidden only if the SSID is actually hidden
Ticking it for a visible network produces a code that many phones accept and some reject. The generator cannot verify this for you; it is a fact about your router, not about the code.
Fill the label, then download PNG and SVG
The label becomes the file name — staff-wifi, guest-wifi,floor-2. Take the PNG for anything you print on paper and the SVG if a designer will place it in a layout, because vectors stay sharp at any size.
One thing this page cannot do: generate all six codes in a single batch. It makes one code per download, so the loop above is the workflow — about two minutes per network, four networks in one coffee. If you only need varied URLs in bulk,that is a different page.
Where these codes actually go in an office
Placement decides whether a code helps or creates a new question. Six positions cover most buildings, and none of them need a design budget.
Reception desk, guest code only. A5, matte, at sitting eye level — not lying flat where it catches the overhead light. This is the single highest-traffic code in the building and the one that should never be the staff code.
Inside each meeting room, beside the door. The room code earns its keep the first time a visitor's laptop cannot reach the guest network from a corner of the room, and the second time you want the room's password changed without touching the office.
Floor plates and stairwell exits. Staff codes belong where staff already walk past — by the lift bank, at the top of each stairwell. Print them at 4 cm or larger; smaller codes survive on paper but fail on the slightly dusty glass or the laminated sheet that has been wiped twice a week.
The print room or device cluster. This one is filed, not posted. Devices rarely scan, but the person who reprovisions them will want the credentials in one place. Keep it with the asset list, in the same drawer as the router documentation.
Never in the lobby, and never in a photograph. Anything a visitor can see from a waiting chair has effectively been published. That includes the back of a monitor at a hot desk, which is where people tape things when they assume nobody notices.
Size and contrast matter more than you would think: the printing guidance onthe generator page covers the practical minimums, including why gloss lamination hurts a scan.
What breaks in an office that never breaks at home
Four failure modes, all of them office-specific. None can be fixed by the code, so each one needs a line in your rollout plan rather than a cleverer QR design.
Corporate login networks cannot be encoded. If users sign in with a company account, a certificate, or 802.1X, there is no field in the WiFi QR format for that. Any tool that promises it is generating something your phone will reject. Staff on those networks join the way they always have.
MAC randomisation makes per-device codes pointless. Modern phones present a different hardware address per network by default, so a code "tied to a device" is not a thing you can build with a static QR. Device-level control is a controller feature, not a code feature.
Hidden SSIDs behave differently across phones. The hidden flag is standard; how reliably each platform honours it is not. Test one Android and one iPhone before you print forty signs, and prefer unhiding the SSID where policy allows — a hidden network name is not a security control, and it costs you a whole class of support calls.
A captive portal turns the code into a page link. If the network shows a login page before granting access, scanning the code gets the phone onto the network and then straight into that page. That is fine — it is the intended flow — but the sign should say "scan, then sign in" so nobody concludes the code is broken. The same applies when a room's display shows a pairing page rather than a network.
Rotating the staff password without reprinting every floor
This is the moment the plan pays for itself. When the staff password changes, only signs holding the staff network need to be replaced: the floor plates, the meeting-room code if that room is on the staff network, and the stairwell copies. The guest code at reception does not change, because it was never the same network.
What you cannot avoid is reprinting. A static code carries the password in plain text; once the password changes, every printed copy of that code is obsolete. That is the honest cost of printing, and it is exactly the reasona dynamic code exists as an alternative for the networks you rotate most often.
Two habits make rotation cheap. Keep the label on every file, so the reprint list is a folder listing and not an afternoon of walking the building. And print the change date in small text under each sign — the next person to inherit this will otherwise have no idea which of six similar-looking codes are still current.
Office WiFi QR code questions
Can one code serve the whole office?
It can, and that is what most offices do — one code, one network, everyone on it. The cost shows up on the day you need one person off the network: with a single code and a single password, removing a contractor means changing the password for everybody, then reprinting every sign.
What happens when an employee changes phones?
Nothing. The code carries the network name and password, not a device. A new phone scans the same sign. Device-level control needs a system this cannot do — see the answer about corporate login below.
Should the meeting room have its own code?
Only if the room already has its own network, or you want to be able to change its password without touching the office one. Two conditions are worth the extra sign: guests book the room regularly, and someone senior uses it for calls you would rather not have on the open guest network.
Can these codes be used by printers and other devices?
Devices with a camera or a scanner and a WiFi setup screen can use a code the same way a phone does. Most office printers cannot scan one — for those, type the credentials once and keep a filed copy of the code for whoever reprovisions the machine.
Is a hidden network a problem?
It is a risk, not a blocker. The code can carry the hidden flag, and phones that support it will still join. Behaviour differs between Android versions and between iOS releases, so test on one phone of each before printing forty signs. If the test fails, unhide the SSID or accept manual entry.
Can I make a code for a WiFi network that needs a company login?
No. The WiFi QR format stores a network name, a password, and an encryption type. Corporate networks that authenticate each user with 802.1X, a certificate, or a Microsoft or Google sign-in do not fit in that format, and a code claiming otherwise will scan and then fail. Those users join the usual way, through their device profile.
One network, one sign
Generate the office code above, or start from the WiFi pages that explain the fields.