Coming soon · summer 2026

Your restaurant's QR menu opens a PDF.
Your guests are giving up.

TealStag is a manual-first menu editor for independent restaurants. Until we ship, run our 10-row mobile menu audit — no signup.

No waitlist form. Bookmark us if it's useful.

9:41 5G
menu.pdf · 7.8 MB
SUMMER MENU — page 2 of 6
STARTERS
Bruschetta al Pomodoro 9
Burrata, peach, basil oil 14
Tuna tartare, sesame, lime 16
Charred shishito peppers 11
PASTA
Tagliatelle al Ragù 21
Cacio e Pepe 18
Linguine vongole 24
Truffle pappardelle 28
MAINS
Pan-seared halibut, capers 32
Wagyu skirt steak, frites 39
Saffron risotto 26
Wood-fired branzino 34
pinch to zoom

Today: PDF menu

9:41 5G
Harbor Bistro · Dinner EN / ES
Small plates
Burrata + peach D $14
Charred shishitos $11
Tuna crudo F $18
Mains
Pan-seared halibut F $32
Saffron risotto G $26
Wood-fired flatbread G $17
Tap to call

With TealStag

10 checks

in the mobile menu audit

0 PDFs

forced on your guests

2.5s LCP

target on a slow-4G phone

3 taps

to find an allergen warning

Useful artifact · no signup

Restaurant QR Menu Mobile Audit.

Four rows previewed below; the full ten live on the audit page.

Example score

Workflow test against a typical PDF QR menu. Yours may score higher.

Score

0 / 10

  1. 01

    Does the menu open without forcing a PDF download?

    Fail

    Pass criterion

    Opens as an HTML page in the browser

    Common failure

    Forces a 4 to 8 MB PDF download before anything is readable

    Workflow test on 5 independent restaurant QR codes scanned 2026-05 — 4 of 5 routed to a PDF.

  2. 02

    Is body text 16px or larger after the phone's default zoom?

    Fail

    Pass criterion

    All items and prices render at 16px+ without pinching

    Common failure

    Rendered text is 8 to 10px because the PDF is sized for 8.5x11 paper

    WCAG 2.2 SC 1.4.4 recommends 200% resize without loss; PDF menus break this.

  3. 03

    LCP under 2.5s on a throttled 4G connection?

    Fail

    Pass criterion

    First contentful menu paint under 2.5s on slow-4G profile

    Common failure

    LCP is the PDF itself — 6 to 9s on slow-4G

    Lighthouse 'Slow 4G' simulation against the source PDF, not an HTML page.

  4. 04

    Can a guest read prices without pinch-zooming?

    Fail

    Pass criterion

    Prices live in a left-or-right column at body size

    Common failure

    Prices are in a 7pt right column requiring 3x pinch zoom

6 more rows

LCP, allergen alt text, deep links, update time, Wi-Fi degrade, tap-to-call, kitchen print.

See full 10-row audit

The pain we keep hearing

You already know. Guests are telling you in reviews.

Four quotes, same complaint: the PDF QR menu.

  • “Showing me an 8.5 by 11 inch PDF menu on my phone screen is not the solution.”

    Axios Columbus reader · Apr 2023 · source S-001

  • “Typically it's just a PDF... pinch and scroll and squint.”

    Reddit r/unpopularopinion · Jan 2024 · source S-002

  • “Too hard to go back and forth between sections of the menu on a phone.”

    Axios Columbus diner survey · Apr 2023 · source S-001

  • “Couldn't buy drinks because the QR code didn't work and there was no other menu.”

    Reddit r/Productivitycafe · 2024 · source S-003

Paper menus cost $4–5K/year per location. A clean mobile page is the third option.

9:41 5G
menu.pdf · 7.8 MB
SUMMER MENU — page 2 of 6
STARTERS
Bruschetta al Pomodoro 9
Burrata, peach, basil oil 14
Tuna tartare, sesame, lime 16
Charred shishito peppers 11
PASTA
Tagliatelle al Ragù 21
Cacio e Pepe 18
Linguine vongole 24
Truffle pappardelle 28
MAINS
Pan-seared halibut, capers 32
Wagyu skirt steak, frites 39
Saffron risotto 26
Wood-fired branzino 34
pinch to zoom

What guests see today

  • Loads as an 8 MB PDF before any text appears
  • Body text rendered at 7–10px, requires pinch zoom
  • No tap-to-call, no allergen alt text, no anchor links
9:41 5G
Harbor Bistro · Dinner EN / ES
Small plates
Burrata + peach D $14
Charred shishitos $11
Tuna crudo F $18
Mains
Pan-seared halibut F $32
Saffron risotto G $26
Wood-fired flatbread G $17
Tap to call

What we render

  • 17px body text, sticky section nav, no pinch zoom
  • Allergen icons with real alt text, tap-to-call number
  • Same QR URL forever, edits ship in seconds

How it works

Replace the PDF menu with a mobile page. Same QR. No POS lock-in.

Three steps. That's the whole product.

  1. 01

    Paste your current menu

    PDF, Google Doc URL, or type it in. You control every field.

  2. 02

    We audit against the 10 rows above

    Same diagnostic, run automatically. Row-by-row report card with one-line fixes.

  3. 03

    Clean mobile page at the same QR URL

    17px body, allergen alt text, tap-to-call. Update a price — the QR doesn't change.

Not at launch: online ordering, POS sync, payments, PDF OCR. Toast and Square already do those well.

Why this exists · Tier 1 proof

We have not shipped yet. Here is the evidence we are building on.

Diner complaints are public and repeat

Axios and Reddit, same story: guests scan, get a PDF, give up. Catalogue in our 2026 teardown.

Sources: S-001, S-002, S-003, S-005, S-006

Owners have a reason to keep digital menus

Axios: QR menus save $4–5K per location/yr in printing. The choice isn't QR vs paper — it's PDF vs mobile.

Source: S-004 (Axios Twin Cities, accessed 2026-05-25)

Accessibility regressions are documented

PDF menus fail WCAG 2.2 SC 1.4.4 and 1.4.10 by default. A clean HTML page passes both.

Sources: S-007 (BYK Digital), S-008 (WCAG 2.2)

What we will not claim

  • No customer testimonials — we haven't shipped yet.
  • No "10x more conversions" claims — nobody has that data honestly.
  • Our wedge is the audit + manual-first editor, not POS replacement.

Found a row your menu fails? Email hello@tealstag.com with the screenshot — we read every one. No form, no list, just a reply.

FAQ

Quick answers before you bookmark us.

Who is TealStag actually for?

Independent restaurants, cafés, bars, and food trucks (especially in tourist markets) who already have a QR sticker on their tables but link to a PDF menu. Also small hospitality consultants who audit menus for clients. It is not for chains running a POS-locked menu stack — Toast or Square already do that well.

What does the product actually replace?

Three things: the PDF you're hosting on Google Drive or your website, the manual export-and-reupload workflow when prices change, and the workaround of printing paper menus alongside the QR. You keep your QR sticker — only the URL behind it changes.

When does it launch and is there a waitlist?

Targeted launch is summer 2026. There is intentionally no waitlist form on this site — bookmark the blog and check back when it's live.

Is it free?

Pricing isn't finalised because we haven't shipped yet. Realistically: one branded menu free, custom domain and multiple menus likely a small monthly fee in the $9–19 range based on what comparable independent-friendly menu tools charge. We will publish the pricing page only when we can actually deliver it.

How is this different from Toast, MenuTiger, Menubly, or BentoBox?

Those tools either come with a full POS stack (Toast, Square), include a lot of restaurant-marketing surface area an independent doesn't need (BentoBox, Popmenu), or have signed up dozens of restaurants at once. TealStag is intentionally one-page-per-restaurant, manual-first, with no POS lock-in. We made the comparison explicit in our 2026 honest comparison post.

What data does the site collect?

Vercel Analytics (page-view-level, no cookies, no personal IDs) and Vercel Speed Insights (Core Web Vitals). No tracking pixels, no third-party ad scripts, no email scraping. The 10-row audit on this page runs entirely client-side — we do not log the URLs you paste in your head.

What does the 10-row audit do exactly?

It is a static scorecard, not a scanner. You read each row, mentally check your own QR menu against the pass criterion, and you know which rows you fail. It is the same audit our editor will run automatically once it ships — we published the criteria first so the methodology is auditable.

Why no signup form?

Email forms on coming-soon pages create a vanity number that doesn't predict revenue. We'd rather earn one returning visitor who used the audit than 200 emails who never come back.

Where can I learn more?

Posts live at /blog. Source ledger is on GitHub. The launch post will go up here on launch day.

How do I get help?

Email hello@tealstag.com. We read every message. Bring a screenshot of the audit row your menu fails and we’ll point you at the post that covers the fix.