About VMenu

VMenu.com started in 1997 with a simple idea: when you’re hungry, you want to see the menu — not a review, not a photo gallery, the actual menu. So we built a directory of local restaurant menus and put it on the web.

The early years: Perl and flat files

The first VMenu was hand-coded in Perl, with restaurant data stored in plain flat files. Every menu was typed in by hand, one dish at a time. It was slow, it was gloriously simple, and it worked — diners in the Dallas suburbs suddenly knew what was for dinner before leaving the house.

Growing up: ASP and SQL Server

As the directory grew from a handful of restaurants to hundreds, flat files gave way to a real database. VMenu was rebuilt on ASP with SQL Server, adding features that became local favorites: the 1999 feature filter set (patio? full bar? delivery?), printable coupons, daily specials, and a reviewer community that ranked the most dedicated local diners.

Today: the modern rebuild

This version of VMenu is a ground-up rebuild on Next.js, React, and Postgres — the same directory soul, with a modern engine. Menus are fully searchable dish by dish, hours drive a live Open Now page, specials and coupons are browsable by type, and the whole thing is city-based so it grows town by town, just like the original.

What hasn’t changed

• Menus first. The menu is the product — searchable, complete, and easy to read.
• Local focus. A city-by-city directory curated by people who eat there.
• Real reviews. Written by actual diners, never paid for, never inflated.
• Free listings. Restaurants don’t pay to be in the directory.

Twenty-nine years in, the mission is the same one we started with in 1997: VMenu finds a menu for you.