Google Drive QR Code Generator
Paste the share link for any Google Drive file or folder and QRKIT turns it into a scannable code. The step that decides whether it works comes first: set the file to “Anyone with the link” in Drive, or your code opens an access-request screen instead of your document. Prefer to skip Google permissions altogether? There is a second route below that hosts the file for you, so a scan never touches Drive at all.
Pattern
Eyes
Do this first
Get the Sharing Right Before You Get the Link
When a Drive QR code fails, the cause is usually the same one, and it has nothing to do with the code. The file was never opened up. Drive keeps new items private by default, so the link works beautifully for you — you are signed in as the owner — and stops dead for everyone else.
So the order matters. Set the sharing, copy the link Drive gives you, and only then make the code. Doing it the other way round is how people end up with a printed square that scans perfectly and opens nothing.
In a browser, on a computer
- 1
Select the file or folder in Drive and click Share.
- 2
Under General access click the down arrow. It will usually say Restricted. Change it to Anyone with the link.
- 3
Set the role beside it. For a file in your own Drive the three choices are Viewer, Commenter and Editor. For anything you are printing, Viewer is the answer — see the warning below.
- 4
Click Copy link, then Done. Copy link is the step Google itself points you at, and it gives you the share URL for the item — which is the address you want carried on something printed, rather than whatever view you happen to have open in the address bar.
In the Drive app on a phone
Same shape, two different labels. Select the file and tap Share. Under General access tap Change and select Anyone with the link, pick the role, then tap Copy link and Back. You can then paste it straight into the generator on this page — the whole job is doable from a phone.
Choose Viewer, not Editor. Editor means anyone who scans your poster can rewrite, reformat, or delete the original document. On a code that is going out into the world, that is a door you cannot close again once the poster is on the wall. Commenter has its place for a draft you want feedback on; Viewer is the right default for everything you print.
One honest test. Open the copied link in a private browsing window, or on a phone signed out of your Google account. If the document appears, you are done. If you see an access-request screen, the sharing did not take — and the permission-trap section below explains the four reasons why. Checking this takes fifteen seconds and is the difference between a print run that works and one that does not.
Three steps
How to Make a Google Drive QR Code
With the sharing already sorted, this part takes about a minute. Designing and previewing need no account at all; downloading the finished file needs a free one.
Share the file and copy the link
General access set to “Anyone with the link”, role on Viewer, then the Copy link button. That button, not the address bar.
Paste the link into the generator
Drop it into the URL field above, then add your logo and colors. The code previews live, so you can check it before you commit.
Test it, then download and print
Scan the preview from a signed-out phone first. Downloading needs a free QRKIT account and gives you a PNG up to 1024px; the SVG for a print shop, and PDF, come with any paid plan. No watermark on any plan.
How it works: this is a standard URL QR code that opens your Drive link when scanned. QRKIT does not connect to Google, never asks for access to your Drive, and cannot see or change the file or its permissions — it points a code at the address you paste. Google Drive and Google Workspace are trademarks of Google LLC; QRKIT is not affiliated with, endorsed by, or integrated with Google.
The failure that ruins print runs
Why Your Drive QR Code Says “Request Access”
Here is the shape of it. You make the code, you scan it on your own phone, the document opens, you send a thousand flyers to print. Then the requests start arriving in your inbox — one per person who tried to read the thing you handed them.
Your test was rigged and you could not have known: your phone was signed in as the owner of the file. Access was never the code's to grant. Drive decides who gets in, entirely on the basis of that item's own sharing settings, and it makes that decision after the scan has already succeeded.
Which is worth stating plainly, because it changes where you go looking when something breaks: a QR code cannot grant access to a Drive file, and no generator anywhere can. The square carries an address. Permission lives with Google. If a scan lands on an access-request screen, the code did its job and the sharing did not.
Four things cause it, starting with the most common.
The file is still Restricted
The default state of anything in Drive. It opens for you because it is yours, and for nobody else. This is the usual cause, and the fix is the walkthrough above.
A Workspace admin blocks link sharing
On a work or school account, an administrator can switch external sharing off or limit it to allowlisted domains. That setting sits above yours, so the option is greyed out or refuses to hold. The nastier version is delayed: a policy change made months later can revoke link access that has been working all along, and every printed code pointing at that file goes dark at once, without anyone touching the file. If a code needs a long life, that is the argument for hosting the document somewhere you control.
The scanner is signed in to the wrong account
A phone already signed in to a personal Google account can be refused a file shared only inside a company. Nothing on your side is wrong; the fix lives on their device, which is exactly why it should never be a printed instruction.
The file was only shared by its folder
This one turns on where the access came from. A file that was never shared in its own right, and is reachable only because it sits in a shared folder, is living on borrowed permissions — move it into a private folder and it loses them, while the printed code keeps pointing at it. A file you set to “Anyone with the link” directly, which is what the walkthrough above has you do, carries that setting with it.
One document or a whole shelf
A Folder Code Is a Handout That Keeps Growing
Folders share exactly the way files do — select the folder, Share, General access, Anyone with the link, Copy link — and the resulting code opens the folder listing, so whoever scans it can browse and pick what they need.
The interesting part is what Google does with permissions underneath. Sharing settings applied to a folder propagate to the files and subfolders inside it, and anything you add to that folder afterwards inherits them too. So a folder code is not a snapshot. Put next term's worksheets, this quarter's price list, or the revised assembly guide into that folder and every code already printed reaches the new material without you doing anything at all.
That inheritance cuts both ways:
- Use a folder when the material is plural or will grow — course packs, a product's documentation set, brand assets, event paperwork.
- Use a single file when there is exactly one thing to read and any extra choice is friction — a price list, a one-page guide, a form.
- Never share a working folder. Make a publishing folder that holds only what you are happy to publish, and copy material into it. Sharing the folder you actually work in exposes everything it contains, including what lands there next week while you have forgotten the poster exists.
One practical note about what a scanner sees: a folder opens as a list of file names on a phone screen. Name things for the reader rather than for you — Assembly guide (2026 model) beats final_v4_REAL_final, and the difference shows up on a four-inch screen more than it ever does on your desktop.
File link
Opens one document, straight away, no choosing. The sharper ask, and the right one when there is a single thing to read.
Folder link
Opens a browsable list, and keeps reaching whatever you add later. One printed square covers a growing set.
Audit before you print
Open the folder as a stranger would and read the file names back. Whatever is in there is part of your handout now.
The other route
Or Skip Drive Entirely and Host the File With QRKIT
There is a second way to do this that removes the permission problem rather than solving it. Instead of pointing the code at Drive, upload the document to QRKIT and let the code open a hosted copy. Nobody meets a Google screen, because Google is not involved. It is not automatically the better choice — the comparison below is honest about where each one wins.
Point the code at your Drive link
- No size ceiling from us — the file stays in Drive, so a large slide deck or a scanned brochure is no problem on any plan.
- The document stays where your team already works on it, and the link always resolves to the current state of it.
- A folder link keeps reaching material you add later, which nothing hosted as a single file can do.
- Sharing has to be right, and can be changed out from under you by a Workspace administrator.
- Google shows your name and email to anyone the link reaches, as the owner of the file.
Upload the file to QRKIT
- No permission screen, ever. A scanner opens the file the way they would open any web page.
- Swap the file later from your dashboard and the printed code follows, with no version-history steps to remember.
- Nothing about your Google account is exposed, because there is no Google account in the chain.
- Upload size is capped by plan — 2MB on Free, 20MB on Starter, 30MB on Plus, 40MB on Pro, 60MB on Ultra and Agency.
- A file QR code is always dynamic, so it uses the single code a free account gets in the dynamic table.
How to actually choose. Start with the file size, because it settles most of these decisions on its own. A free account uploads up to 2MB, which comfortably holds a one-page PDF and does not hold a presentation, so if the document is heavy and you are not on a paid plan, the Drive link is the free-friendly route and there is no shame in it. If the file is small, or you are on a plan that lifts the ceiling — 20MB on Starter, 30MB on Plus, 40MB on Pro, 60MB on Ultra and Agency — hosting it here removes an entire category of failure. And if the document is genuinely collaborative and colleagues edit it weekly, keep it in Drive: the link tracking a living document is the whole point of Drive. If you want the upload route, the file QR code generator is where it starts.
After it is printed
Change the Document, or the Destination, Without Reprinting
Documents move. A file gets superseded, a folder gets reorganized, someone leaves and their Drive gets tidied, or the whole team migrates to a different account. Any of those turns a printed code into a dead end — unless you have one of two escape routes, and it is worth knowing that they are different.
Inside Drive there is a version-replacement feature most people never find. Google keeps the item's identity separate from its contents, so you can put a new document inside an existing one: with the file selected, open More and choose Manage versions, then upload the replacement. The address does not change, which means nothing you have printed needs to. Two limits worth knowing up front — it is a browser feature rather than a phone-app one, and it applies to files you uploaded, not to Google's own Docs, Sheets and Slides, where you just edit the document and the link stays put regardless.
Inside QRKIT: a URL QR code made here is dynamic by default. The printed pattern holds a short QRKIT link and the real destination lives in your dashboard, so you can edit where it goes whenever you like. That covers the cases Drive cannot: pointing the code at a completely different file, at a folder instead of a file, or away from Drive altogether and at a copy hosted here.
The second route is the one that survives a migration. If your organization moves off Google, every static code pointing at a Drive address dies with the account; a dynamic code just needs a new destination typed into a field.
If you would rather not have a redirect in the chain at all, the Dynamic/Static control in the generator lets you switch a link code to static, which bakes the Drive address into the pattern itself. It cannot then be repointed or counted — but it does not depend on a QRKIT account either, and static codes do not count against the one code a free plan allows in the dynamic table. Both are legitimate; pick deliberately rather than by accident.
The other half of dynamic: because scans pass through QRKIT before Drive opens, they can be counted. A free account sees four numbers — total scans, unique scans, top location, top device — while the geo and device breakdown tables, the charts and custom date ranges, and CSV export come with paid plans. Free keeps 30 days of scan history and paid plans keep two years. It tells you how many people reached the document — not how many read it, which is a question neither we nor Drive can answer for you.
Two free-plan limits to check before a print run. First, a free account gets 100 scans a month across the whole workspace, and it is a hard stop: once that number is reached the code stops forwarding and serves a scan-limit page until the monthly reset. A poster in a busy corridor or a code on a product insert can burn through that in days, and a handout that goes dead halfway through term is precisely the failure this page exists to prevent — so size the plan to the placement before you order. Second, a free dynamic code shows a brief “Powered by QRKit” screen on the way through. Any paid plan lifts the cap and removes that screen.
Where it earns its keep
What People Actually Print Drive Codes On
The pattern is always the same: paper is finite and cannot be updated, and the document is neither. A code is the seam between them — it lets a printed thing stay short while the material behind it stays current.
Handouts that outlive the handout
One sheet in someone's hand can only hold one sheet's worth of material. A code at the foot of it opens the full pack — the appendix, the worked examples, the version with the diagrams that would not fit.
Posters and noticeboards
A poster has room for a headline and a code, and not much else. Point the code at the folder holding the timetable, the forms, and the map, and the wall stops being a dead end.
Product manuals and setup guides
Printing a manual into the box locks the instructions to the day the box was sealed. A code on an insert card opens the current guide instead, which matters most for the products whose setup steps keep changing.
Class and course materials
A folder code on the syllabus, the classroom wall, or a worksheet gives students one square that reaches everything for the term. Add next week's material to the folder and the code already reaches it.
Portfolios and sample work
A code on a business card, a print, or a leave-behind opens the full portfolio — the case study, the reel, the drawings at a size a card cannot show. It travels in a wallet and resurfaces long after the conversation.
Client and vendor packs
Onboarding documents, spec sheets, brand assets, price lists. A code on the cover letter or the invoice opens the shared folder, and the folder is the thing you keep current rather than the paperwork.
A few practicalities that apply across all of them. Write three words beside the code saying what it opens — Scan for the full guide — because a bare square asks for trust it has not earned. Size the code to the distance it will be read from, which the QR code size guide covers in numbers. And if you want a separate code per placement so the scan counts tell you which one is working, note that a free account holds one code in the dynamic table, so that setup needs a paid plan. For a whole set at once, the bulk generator builds them from a spreadsheet in a single pass.
Getting it onto paper
Which File You Download, and Why It Matters
Drive codes tend to end up on documents rather than shopfronts — a worksheet, an insert card, a page footer, the corner of a poster. That means they are usually printed small, and small is exactly where a low-resolution file shows its seams: the modules blur into each other and a phone that would have read it instantly starts hunting.
From the generator above, a free account downloads PNG at up to 1024px. That is genuinely enough for slides, an email, and anything you run off on an office printer at handout size. The SVG is the vector export and ignores the pixel ceiling entirely, so it is what you send a print shop for a poster or a banner — and it comes with a paid plan, which is worth knowing before you promise a printer artwork by Friday.
Do not mistake the generator's PDF for press artwork: it places a 1024px image on an A4 page, which makes a fine proof and a poor master — and, like the SVG, it needs a paid plan. Once the code is saved to your dashboard, re-downloading it from there also gives you a genuinely vector PDF and an EPS, on a paid plan as well: vector exports are gated on that surface too, so a free account gets PNG in both places. There is no watermark on any download, on any plan, including Free.
Whichever file you print from, print one and scan it on two or three different phones before you commit to a run — and do that test from a phone signed out of your Google account, so you are checking the sharing and the printing in the same pass.
Branding it is free. Your logo in the middle and your colors on the pattern come with every plan, Free included — start from the branded QR code generator if you want every code you print to match. What actually decides whether a code scans is contrast and the clear margin around it, not the logo, so keep the code dark on a light background and leave the border alone.
Nearby, but different
Is This the Right Page for What You Are Sharing?
“A QR code for a Drive file” covers several different jobs, and some of them are better served elsewhere on this site. Worth ten seconds before you print anything.
It is a Google Doc, Sheet, or Slide deck →
Google's own document types behave differently from uploaded files — different roles, different editing behavior, no version-upload step. QR codes for Google Docs covers that lane in full.
You would rather host the file yourself →
The upload route, in detail: supported types, what opens in a phone browser and what downloads instead, and the size limits by plan. File QR codes is the place to start.
The file lives in Dropbox instead →
Same job, different sharing model and a different set of traps. Dropbox QR codes walks through the link settings that matter there.
It is a PDF and you want it to just open →
PDFs are the most-printed document type and the most particular about how phones render them. PDF to QR code is written for that case specifically.
It is a spreadsheet or a price list →
Wide tables are the hardest thing to read on a phone, and there are ways to make it bearable. Excel QR codes goes through them.
Because a Drive code is a URL QR code underneath, the same generator handles every other link you have — build one for anything with the URL QR code generator. Wondering how long any of this lasts? Do QR codes expire answers it for both kinds. If the code is going on something adhesive, QR code stickers covers material and finish, and scan tracking tells you which placement is pulling its weight.
Google Drive QR Codes — Frequently Asked Questions
Google Drive, Google Workspace and Google Docs are trademarks of Google LLC. They are referred to here only to describe the kind of link a QR code can open. QRKIT is an independent QR code generator, is not affiliated with or endorsed by Google, and has no integration with Google Drive: it never connects to your Drive, never requests access to it, and cannot read or change your files or their sharing settings.
Sharing set? Then you are a minute away
Make Your Google Drive QR Code
Set the file to “Anyone with the link”, paste the link Drive gives you, and download a code that opens your document for anyone who scans it — no Google account required at their end.