Skip to content

After the Scan › Episode 8

Static File or Hosted Card

Making a digital business card takes about two minutes in a browser. Five mistakes account for most of the ones that fail, and one tradeoff decides which kind you want.

September 16, 2026 · 3:36

Also wherever you get podcasts – the feed is at https://podcast.whooshly.co/feed.xml.

Full transcript

Every word, as recorded

Making a digital business card takes about two minutes in a browser, with no app and no signup. Open a vCard maker, type your name and title and company and number and email, generate the file and a QR code, done.

The two minutes are not the hard part. Five mistakes account for most of the cards that fail in the wild.


Quick ground rule first. What you are making is a vCard, an open standard from the IETF, so an iPhone and an Android both read the identical file. You are not buying into anyone's format.

Now the five.

The first is cramming the whole vCard into the QR code. A QR maxes out around two thousand nine hundred and fifty three bytes, and a contact file with a photo in it gets close to that quickly. Point the code at a short link instead. It scans faster, it stays editable, and the printed square gets smaller.

The second is an oversized photo. A heavy embedded image bloats the file and the code together. Shrink it, or put it on a hosted card and keep the file lean.

The third is skipping the test scan. One iPhone, one Android, before you print or share anything. In our testing across events, this is the step people skip and the one that would have saved them, because a card that will not scan at a booth is a lead you lose in silence. Nothing gets said. They smile and move on.

The fourth is a dead link. A hosted card that returns a not-found page is worse than no card at all, because the other person already decided to save you and then watched it fail. Re-check the address after every edit.

And the fifth is a stale job title on a static file. A vCard cannot be recalled once it has been shared. If your title moves, that is a hosted-card problem, not a file problem.

That is the one tradeoff, and it decides the whole thing.

A static file freezes at the moment somebody downloads it. Whatever it said is what sits in their phone from then on. That is a fine answer when your details are stable, and it is free, and it needs no account and no company to stay in business.

A hosted card sits at a link and stays current, because you are editing the page rather than the copy they took. That is what you want when your details move, or when you want to know whether anyone opened it.

So the order is: start free. Make the file, point the QR at a link, keep the photo small, test-scan it on both platforms, and share it. That covers a lot of people completely.

Upgrade when the tracking earns it, and not before. If you want a card that stays editable after you have handed it out, and you want to see that it was opened, that is a real reason to pay for something. Wanting a nicer template is not.

We give the free version away deliberately, and we would rather you used it and paid us nothing than paid us for something you did not need. A nicer template is not a reason to start a subscription.

And whichever you land on, check one thing before you commit: if you stop paying, does the card stay up? On a static file the question does not arise. On a hosted one, it is the only question.

I am Ankur, and I built Whooshly. Digital cards, QR codes and short links you pay for once instead of by the month. If you want the card you handed someone to still open next year, we are at whooshly.co.

Where this comes from

Every fact in this episode traces to one article

We do not write episodes from memory. This one is drawn from a single published piece, and the sourcing and method are set out there in full.

Read the article

The tools this episode is about

Short links, dynamic QR codes, UTMs and digital cards on whooshly.co – paid for once, with the permanence pledge attached.

Whooshly / AI assistantAsk Whooshly

Answers about products, pricing, and setup.

What do you want to make?

Ask about links, QR codes, UTMs, pages, pricing, analytics, or custom domains.