Setup guide · US & Canada
Web Browser AR Menus: Safari and Chrome, No App (2026)
Guests scan QR and preview dishes in the browser, no download. Free 3 AR dishes, setup guide for US and Canada restaurant owners.
2026-08-18 · 9 min read · BeforeTable
What an augmented reality web browser menu actually is
An augmented reality web browser menu is a mobile web page guests open in Safari or Chrome after scanning your table QR code. Selected dishes show a 3D badge. Tapping the badge launches WebAR preview inside the browser without a guest app download.
This is not a separate AR browser app from an app store. It is your menu URL using web standards so iPhone Safari can hand off to Quick Look and Android Chrome can open Scene Viewer on supported devices.
BeforeTable hosts the menu, models, and QR link for US and Canada independents. Definition for staff cards: beforetable.com/blog/what-is-an-ar-restaurant-menu.
Browser-first versus native app menus
Native apps require install friction before the first bite. Web browser menus keep turnover high because scan opens the page guests already use daily.
Text menu always loads first
Every line item stays readable text with prices and allergens. 3D assets fetch only when guests tap a hero tile.
Why augmented reality web browser menus matter in 2026
US and Canada dine-in traffic runs mostly on iPhone Safari and Android Chrome. Building AR only inside a custom app excludes guests who will not install software for a one-hour meal.
Owners search augmented reality web browser because they want proof that AR works on the phones already at the table, not on a demo iPad locked in the office.
WebAR also survives app store policy changes and OS updates better than a bespoke guest app you must rebuild each year.
No download objection removed
Train staff with one line: Scan for our menu. Tap 3D to preview. No download needed. FAQ backup: beforetable.com/blog/do-customers-need-app-ar-menu.
Same URL on tent and Google
One stable menu link on table tents, receipt inserts, and Google Business keeps browser AR behavior consistent across discovery and dine-in.
Safari WebAR path for iPhone guests
Guest scans QR, taps Open in Safari, browses text categories, taps a dish with a 3D badge. Safari loads the model and may open Quick Look for AR placement on the table surface.
Quick Look is Apple's system viewer for USDZ assets. Guests rotate the dish, check height against the table edge, close viewer, return to menu list.
Deep browser guide: beforetable.com/blog/webar-menu-safari-chrome. iOS-specific notes also live at beforetable.com/blog/ios-quick-look-restaurant-menu when you train floor staff.
Test from seated height
Scan from a chair, not standing over the table. Pendant glare and patio sun expose bad laminate before bulk print.
Fallback when Quick Look does not open
Inline 3D rotation still sets portion expectations when table placement is unavailable. Honest preview beats hiding the feature.
Chrome WebAR path for Android guests
Guest scans QR, opens Chrome banner, browses menu, taps 3D tile. Chrome loads glTF and may hand off to Google Scene Viewer for table placement on ARCore-capable phones.
Scene Viewer is not a restaurant app. It is a system shell that displays your model from the menu link. Android guide: beforetable.com/blog/android-scene-viewer-food-menu.
Test a mid-range Android phone your servers carry, not only a flagship demo unit. Behavior varies by Chrome version and ARCore support.
Camera permission is normal
Scene Viewer may ask for camera access for table placement. Staff should know that prompt is expected and not a sign the guest must install an app.
Return path to text menu
After closing Scene Viewer, the guest should land back on the same dish list. Test back navigation on target Android devices before Saturday service.
Technical requirements for browser AR menus
Models must serve over HTTPS from your menu host. BeforeTable delivers glTF and USDZ when dish status shows Ready in the dashboard.
Page load should stay text-first so venue LTE does not stall on ten megabyte bundles. Hero models fetch on tap, not on initial scroll.
Adding 3D to an existing QR flow: beforetable.com/blog/qr-code-menu-with-3d-models.
HTTPS and mixed content
Mixed HTTP assets break WebAR on modern browsers. Platform hosting keeps model URLs compliant without owner DevOps work.
Model size and first tap speed
Oversized uploads slow first preview on weak Wi-Fi. Compression at upload time keeps first tap responsive on typical restaurant networks.
Setting up your augmented reality web browser menu
Create a BeforeTable account, upload three hero dish photos, wait for Ready status on each, generate your menu QR, print one test tent, scan on iPhone Safari and Android Chrome from seated height.
Step-by-step ladder: beforetable.com/blog/how-to-create-an-ar-restaurant-menu.
Run one busy lunch on a single section before you reprint every table. Compare guest questions on previewed dishes against your control section still on paper or PDF.
Photography before upload
Shoot consistent angles with even light on the plate you serve. Angle guide: beforetable.com/blog/dish-photography-angles-for-ar-menus.
Wi-Fi signage if LTE is weak
First model load needs bandwidth. A small Wi-Fi card on the tent reduces failed previews in basement dining rooms.
Which dishes to feature in browser AR first
Start with three heroes on Free tier: highest margin plates, shareables that drive portion questions, or signature desserts guests photograph for social.
Avoid three items that look identical on camera. Color contrast helps guests instantly know which tile they tapped in Safari or Chrome.
When a special rotates off, swap the upload in dashboard. Table QR stays the same when it points at your stable menu URL.
Label 3D badges clearly
Use Preview or 3D on hero tiles so guests know which dishes open browser AR. Hidden features get zero taps.
Bar and dining in one URL
Section headers inside the same menu link beat printing second QR codes for cocktail list versus dining entrees.
Pricing for browser AR menus (USD)
Free is $0 USD for 3 AR dishes. Starter is $20/mo for 15 dishes. Growth is $200/mo for 50 dishes plus analytics. Enterprise is custom for multi-location operators.
Safari Quick Look and Android Scene Viewer handoffs do not add a separate per-preview fee on BeforeTable. Plan limits define how many simultaneous WebAR heroes you can publish.
Full breakdown: beforetable.com/blog/beforetable-pricing-explained.
When Starter beats Free
Upgrade when seasonal rotations need more than three simultaneous browser AR heroes live or when guests ask for preview on more than three signatures.
Compare to custom WebAR builds
Agency WebAR projects often cost five figures before first service. BeforeTable fits independents who need proof on three dishes first.
Troubleshooting browser AR at the table
Scan fails: move tent out of glare, wipe matte laminate, verify QR quiet zone, type short URL printed below code.
Preview fails: confirm dish shows Ready in dashboard, retry on Wi-Fi, test second device. Never blame the guest phone on a busy Friday.
Keep paper backup for guests who decline phones. Allergy protocol stays verbal even when digital menu lists allergens.
Wrong browser opened
Some Android cameras open Samsung Internet or Firefox. Train hosts to tap Open in Chrome when the banner appears.
Preview honesty
If kitchen plating drifts from the 3D hero, update photos. Guests notice mismatch most on items they previewed in the browser.
People Also Ask: augmented reality web browser menu
Owners ask whether WebAR needs an app, which browsers work, and what USD plans include. Twenty FAQs below mirror those phrasings with Safari and Chrome facts.
Search phrases to match
AR menu in browser? WebAR Safari Chrome restaurant? Align FAQ text to those strings for AI Overviews.
Link pillars in body copy
Point readers to definition, how-to, pricing, iOS Quick Look, and Android Scene Viewer posts for crawler clustering.
Launch your augmented reality web browser menu this week
Upload three heroes, wait for Ready, generate QR, print one test tent, test Safari and Chrome on Saturday lunch.
Augmented reality web browser menus work when scan access, WebAR preview, and kitchen output tell one honest story.
When three heroes are not enough, upgrade to Starter for fifteen slots without changing QR artwork guests already know.
Frequently Asked Questions
What is an augmented reality web browser menu?
A mobile web menu guests open in Safari or Chrome after scanning a QR code, with optional 3D dish preview in the browser without a guest app download.
Do guests need an app for browser AR menus?
No. WebAR runs in Safari or Chrome after scan. See beforetable.com/blog/do-customers-need-app-ar-menu.
Which browsers support restaurant WebAR?
Test iPhone Safari and Android Chrome before launch. Those cover most dine-in guests in the US and Canada.
How does Safari show AR on a restaurant menu?
Guests tap 3D dish tiles and Safari may open Quick Look for table placement. Details at beforetable.com/blog/webar-menu-safari-chrome.
How does Chrome show AR on a restaurant menu?
Chrome may hand off to Google Scene Viewer on supported Android devices. Guide at beforetable.com/blog/android-scene-viewer-food-menu.
How many AR dishes can I start with in the browser?
Three AR dishes on BeforeTable Free at $0 USD. Starter is $20/mo for 15. Growth is $200/mo for 50.
How do I create a browser AR menu?
Upload dish photos to BeforeTable, wait for Ready, generate menu QR, test on Safari and Chrome. Steps at beforetable.com/blog/how-to-create-an-ar-restaurant-menu.
What is WebAR on a restaurant menu?
WebAR shows 3D dish preview in the browser when guests tap hero tiles. Definition at beforetable.com/blog/what-is-an-ar-restaurant-menu.
Does browser AR work in Canada?
Yes. US and Canada restaurants use the same USD plans and browser WebAR on iPhone Safari and Android Chrome.
Will browser AR slow down my menu page?
No when text loads first and 3D fetches only on tap. Initial scroll stays fast on venue LTE.
Can I use my existing QR tents for browser AR?
Yes. Point existing tent artwork at your BeforeTable menu URL instead of a PDF link.
What if Quick Look or Scene Viewer does not open?
Inline 3D rotation still helps portion clarity. Test devices before launch and keep honest preview on supported paths.
Do I need HTTPS for WebAR menus?
Yes. Models and menu pages must serve over HTTPS. BeforeTable hosting handles this for uploaded heroes.
How do I photograph dishes for browser AR?
Use consistent angles and even light on service ware. Guide at beforetable.com/blog/dish-photography-angles-for-ar-menus.
When should I upgrade from Free to Starter?
Upgrade when you need more than three WebAR heroes live at once or when seasonal rotations exceed three preview slots.
Where is BeforeTable pricing explained?
See beforetable.com/blog/beforetable-pricing-explained for Free, Starter, Growth, and Enterprise USD plans.
Can I add browser AR to a PDF QR menu?
Replace the PDF link with your BeforeTable menu URL on the same tent. Guide at beforetable.com/blog/qr-code-menu-with-3d-models.
Does browser AR require camera permission?
Table placement AR may ask for camera access. That is normal for Quick Look or Scene Viewer and not an app install prompt.
Will browser AR work on older phones?
Older devices may show inline 3D spin without table placement. Plan staff scripts for both paths rather than promising AR on every handset.
What is the first step to launch a browser AR menu?
Create a BeforeTable account, upload three hero dish photos, wait for Ready status, generate your menu QR, and test on iPhone Safari and Android Chrome.