Menu Maker

From an empty page to a menu you can print: add sections, add dishes, and the type is sized for the page.

Checked in a browser on 2026-11-19 · how these tools are tested · runs on your device

From an empty page

Nothing is pre-filled here. Add a section, add dishes, name the restaurant in the title. The same alignment rules apply: the price sits against the right edge and long names are shortened rather than allowed to collide with it.

Sections can be removed as easily as added, which matters while a menu is still being decided. The preview is the document — there is no separate publish step.

    When the menu grows

    A one-page menu reads better than a two-page one, so if the content overflows, cut dishes rather than shrinking the type. The layout stops at the bottom margin on purpose: it does not silently reduce everything to fit.

    Prices are text, so currencies and formats are whatever you type — no symbol is assumed. Download the PNG for a screen, or the PDF for the printer.

      File formats and what changes them

      The PNG is a picture: it cannot be edited afterwards without an image editor, and the text in it is not selectable. That is fine for a menu that goes to a printer, and wrong for one that will be corrected every week.

      The PDF embeds the same picture on an A4 page, so the print dialog has nothing to scale. If a price changes, change it here and download again — the file is generated fresh each time, never edited in place.

        How Menu Maker works

        Start empty and add sections, dishes and prices. Long names shorten rather than push into the price, and the PDF keeps the spacing. The method behind Menu Maker is the single-purpose logic inside wave50.js, and this page shows the result with its assumptions in the open.

        • Open Menu Maker and provide menu maker — the page accepts it in the field it shows.
        • For Menu Maker, canvas and CSS do the rendering; colours are converted mathematically between models.
        • The Menu Maker output appears on the page and can be copied or downloaded in the format it offers; nothing is kept afterwards.

        A worked example for Menu Maker

        A typical run of Menu Maker starts with menu maker and ends with the result shown above; the page reports what it did in plain words so the output can be checked against a known-good case before it matters.

        Export once and open the file at 100%: colours and dimensions are what you set, and any surprise is the font substitution the limits section warns about. That check applies directly to Menu Maker with menu maker.

          When to use Menu Maker — and when not to

          Reasonable uses: Brand colours and palettes; Social graphics at the right dimensions; Print-ready cards and posters. Menu Maker is deliberately narrow: it does one job and states its assumptions instead of hiding them.

          Canva-class tools do more layout, but they also want an account and a canvas that belongs to them. For one card, one palette or one banner, this is faster. The honest ceiling for Menu Maker: for Menu Maker, fonts come from your device, so exact rendering varies.

          • Best case for Menu Maker: Brand colours and palettes
          • Also fine with Menu Maker: Social graphics at the right dimensions
          • Not what Menu Maker is for: for Menu Maker, fonts come from your device, so exact rendering varies.

          Reading the Menu Maker result

          The output of Menu Maker is a function of the inputs alone — no hidden state and no server.

            Accuracy and limits of Menu Maker

            The method is the single-purpose logic inside wave50.js. Menu Maker prints results at the precision its inputs justify, and the limits below are the honest ones:

            • Menu Maker: For Menu Maker, fonts come from your device, so exact rendering varies.
            • For Menu Maker, exports are raster (PNG/JPEG/PDF) unless SVG is offered.

            Privacy and speed on the Menu Maker page

            The Menu Maker page is a static file plus wave50.js; there is no upload endpoint behind it, so your input cannot be stored or logged. Closing the tab discards the work.

            Speed follows the build: Menu Maker loads one stylesheet and one script, with no framework, no web font and no tracker. That is why the tool responds as you type instead of waiting on a round trip.

              What you get from Menu Maker

              The output of Menu Maker appears on this page and can be copied or downloaded in the format the page offers. Nothing is queued, nothing is emailed, and there is no usage counter — the design work finishes the moment the numbers are in.

              Because Menu Maker is built from wave50.js rather than a server call, the practical ceiling is your device: memory for large inputs, and CPU for anything that loops over pixels or pages. On a normal laptop that ceiling sits far above everyday use; on an old phone it arrives sooner, and the page tells you when a job is too big instead of failing silently.

                Questions

                What does Menu Maker do?

                Start empty and add sections, dishes and prices. Long names shorten rather than push into the price, and the PDF keeps the spacing. Everything runs in your browser; nothing is uploaded.

                How accurate is Menu Maker?

                The method is the single-purpose logic inside wave50.js. For Menu Maker, fonts come from your device, so exact rendering varies.

                What are the limits of Menu Maker?

                For Menu Maker, exports are raster (PNG/JPEG/PDF) unless SVG is offered.

                Is anything uploaded when I use Menu Maker?

                No. Menu Maker runs entirely in the browser tab; nothing is uploaded, stored or logged.

                Can I use Menu Maker offline?

                Yes — Menu Maker keeps working offline once the page has loaded; the whole tool is a local script.

                Keep going

                More design tools