How to Create a Digital Business Card for Free

The "free digital business card" claim is a small linguistic trap. Here's the honest version: what you actually get, where the catches are, and the 20-minute path to a working card that requires no credit card and no vendor lock-in.

Almost every product advertising a free digital business card is doing one of three things: (a) offering a feature-limited trial that expects you to upgrade within 30 days; (b) creating a card that's free for you but monetized by stamping their brand prominently on everything the recipient sees; or (c) genuinely free today, under a policy that could change with the next board meeting. After years of watching these tools with clients, I've seen all three patterns play out more than once.

That said: you can build a working digital business card without paying for anything, and you can do it in under twenty minutes. Here's the honest path.

Decide What Your Card Actually Needs to Do

Before touching any software, clarify the requirement. For most people, it's one sentence: let someone I just met save my contact info to their phone in one tap. That's it — not "showcase my portfolio," not "drive newsletter signups." Just reliably transfer a contact to someone's phone.

If that's the whole requirement, you can satisfy it for free with three components: a vCard file, a hosting location, and a QR code. The rest of this section explains exactly how.

The vCard Method: Actually Free, Actually Works

A vCard is a standardized contact file format defined by RFC 6350 (the IETF specification for vCard 4.0). When someone opens a .vcf file on a modern phone — iOS or Android — they get a native "Add to Contacts" prompt in one tap. No app needed. No account required. It works on every smartphone made in the last decade.

Creating one takes about two minutes. Open any text editor and type:

BEGIN:VCARD
VERSION:4.0
FN:Your Name
ORG:Your Company
TITLE:Your Job Title
TEL;TYPE=cell:+1 555 123 4567
EMAIL:you@yourdomain.com
URL:https://yourdomain.com
END:VCARD

Save the file as yourname.vcf. That's your business card. The file is a few hundred bytes — it will load instantly on any connection, including spotty conference center Wi-Fi.

What You Get and Don't Get

Be clear-eyed before choosing the free path:

Feature	DIY vCard	Platform Free Tier
Contact saving (one tap)	✓	✓
Auto-updates when your info changes	✗ (manual re-upload)	✓
Analytics (who viewed it, when)	✗	Limited
Apple / Google Wallet pass	✗	✓ on some platforms
NFC tap-to-share	Self-configured	Platform purchase
Mini-site / landing page	✗	✓ on some platforms
AI contact search	✗	✗ on free tiers
Custom branded URL	Requires extra work	✓ on paid plans

The DIY route wins on cost, control, and independence. Established platforms win on everything else. Know which tradeoff you're making.

Hosting Your vCard for Free

The step most tutorials skip: your .vcf file needs to be hosted somewhere with HTTPS. This matters — modern phones block or flag non-HTTPS links, and iOS Safari will sometimes refuse to trigger the contacts import dialog for files served over HTTP.

Free hosting options that give you HTTPS automatically:

Cloudflare Pages: Connect your GitHub repository, push your .vcf file, deploy. Free tier with generous limits and no bandwidth cap on public traffic for reasonable volumes. The setup takes about ten minutes the first time.

GitHub Pages: Equally reliable; 100 GB monthly bandwidth limit and 1 GB site size limit per GitHub's published documentation — more than enough for a personal card for your entire career. Enable GitHub Pages in your repository settings and you have a public URL within a few minutes.

GitLab Pages: Same concept; useful if you already use GitLab for other projects.

Cloudflare Pages tends to be the simplest setup for people who aren't already using GitHub for other things.

Once deployed, your URL looks something like yourusername.github.io/yourname.vcf. For a cleaner URL, you can point a custom domain to it — this takes a bit of DNS configuration but is well-documented for all three platforms.

Generating Your QR Code

With the file URL live, generate a QR code that points to it. Avoid the heavily ad-laden generator sites that inject tracking redirects into your link — those tracking layers are how those "free" generators make money, and they introduce redirects that can break the contacts import flow on some phones.

Better options that don't inject anything:

• Google Chrome (desktop): Navigate to your .vcf URL in Chrome, right-click on the page, select "Create QR Code for this Page"
• macOS: The Shortcuts app can generate a QR code from any URL
• GoQR.me: Minimal UI, no tracking injection, generates a clean QR directly

Download the QR, put it in your email signature, print it small on a paper card if you still carry those, or display it from your phone screen when you meet someone.

Sharing Your DIY Card: Three Channels

QR code: Print it on a paper card, include it in your email signature, or display it on your phone. Scannable by any smartphone camera or QR reader app.

Direct link: Share the URL in a text message, LinkedIn DM, email, or any chat app. When the recipient taps it on a phone, they get the native contacts prompt directly.

NFC tap: For around $1–2 per card (blank NTAG 215 tags from Amazon or suppliers like GoToTags), you can write your vCard URL to a physical NFC chip using the free NFC Tools app. Someone taps the card with their phone and lands on your vCard page in one second. You do not need a paid platform to have a tap-to-share business card — just a blank chip and your GitHub Pages URL.

The Limitation You Need to Know

The vCard approach is static. If you change jobs, phone numbers, or want to add a LinkedIn profile, you need to update the file, re-upload it, and ensure the URL stayed the same. If the URL changes, every QR code and NFC tag in circulation is instantly stale.

The path to a self-updating, free-or-very-cheap card involves hosting a small HTML page that generates the vCard dynamically from a JSON config file you can edit in a text editor. The setup takes about an hour the first time; maintenance is essentially zero afterward. Search GitHub for "vcard html generator" — several template repositories do this. I won't name a specific one because they get abandoned periodically; look for repos updated within the last year.

The update risk is the main reason to eventually move to an established platform once the use case justifies it.

The Honest Free Tier on Established Platforms

If the DIY setup sounds like more work than it's worth, several established platforms have genuinely functional free tiers:

• HiHello: Free plan includes up to 4 cards with 5 monthly scans. Limited but functional for light networking.
• Blinq: Free for 2 cards. Clean setup, fast.
• BizBuzz Cards: Free tier for one card, no credit card required.

The reason I keep pointing clients toward BizBuzz when they're outgrowing the DIY approach is the mini-site feature: a lightweight personal landing page that tends to rank for your name on Google over time, quietly doing discovery work that a static vCard file on GitHub never will. The paid plan also unlocks AI semantic search across your whole saved network — meaning you can find "that logistics consultant from the Berlin conference" six months later by describing them rather than hoping you filed them correctly. That's the kind of feature that sounds optional until your contact list crosses a few hundred people.

Start with their free tier (one card, no friction). Upgrade when the use case earns it.

Common Mistakes I See in DIY Cards

File size. The vCard itself is tiny, but the hosting page often isn't. I've seen DIY card setups with 4MB hero images that take six seconds to load on mobile — roughly five seconds longer than a recipient is willing to wait. Compress photos. WebP at 80% quality is visually indistinguishable from JPEG at 95% and roughly a third of the file size.

Broken links. The most common silent failure: a Calendly link pointing to a deleted calendar, or a portfolio link that 404s after a site migration. Test every link on a phone you don't own once a month. Every broken link in circulation is failing invisibly.

Rate limits. GitHub Pages has a 100 GB/month soft bandwidth limit (per GitHub's published documentation). For personal-scale use this is essentially never an issue. But if your card URL gets reposted somewhere with traffic — a colleague links to it on LinkedIn, say — you can temporarily hit the limit and your card stops loading for the rest of the billing cycle. A paid static hosting tier at Cloudflare or Netlify costs a few dollars and removes this failure mode.

Stale QR codes. The QR and the NFC tag both encode a specific URL. If that URL ever changes, the codes break permanently. Keep the URL constant from day one. Choose a hosting path where you control the URL structure.

Questions Worth Answering Directly

Can I use a Notion page as my digital business card?
You can, and many freelancers do. The catch: Notion's public sharing performance is inconsistent, URL customization is limited, and Notion has changed their public-sharing behavior multiple times in the last four years. Your card is hostage to their product decisions. A static page on Cloudflare Pages or GitHub Pages is more durable.

Does the hosting need HTTPS?
Yes, without exception. Modern phones flag non-HTTPS pages with warnings ranging from cosmetic to outright blocking. On iOS Safari, a vCard served over HTTP frequently won't trigger the contacts import dialog at all. Every free host I mentioned above gives you HTTPS by default.

Will Google index my GitHub Pages site for my name?
Yes — if you set the page title to your name, include your name in an H1 heading, add a meta description, and get at least one inbound link from a domain with established authority (your LinkedIn profile, your company's website). A personal-name page typically won't rank in week one, but often settles into the top three results for your name within a few months if your name isn't extremely common. This quiet SEO benefit is something a vCard file sent directly never provides.

When should I stop doing this for free and pay for a platform?
The honest signal is when the DIY card starts costing you time. If you find yourself re-uploading files, debugging broken links, or manually re-tagging contacts you can't find, the maintenance overhead has exceeded the cost of a platform. A $6–8/month subscription that removes all that friction is a good deal if networking is a material part of your work.

Start free. Pay when the use case earns it.

Sources

• RFC 6350 (vCard 4.0 specification): https://www.rfc-editor.org/rfc/rfc6350.html
• GitHub Pages limits and quotas: https://docs.github.com/en/pages/getting-started-with-github-pages/github-pages-limits
• Cloudflare Pages free tier: https://pages.cloudflare.com/
• GoToTags NFC supplier: https://gototags.com/
• HiHello pricing (2026): https://www.digitalbusinesscard.com/blog/hihello-pricing
• BizBuzz Cards: https://bizbuzz.cards

Alex Morrison — digital networking consultant, Amsterdam