Digital Menu Board File Format: PNG, JPG or MP4?

Choosing a digital menu board file format is two decisions: which container suits the content, and whether the file matches the screen it will play on. Get the second one wrong and the sharpest artwork still looks soft, letter-boxed or cropped.

Start with what your player accepts. Requirements differ between systems, so the settings below are worked examples to reason from rather than universal rules. Confirm your own player's accepted formats and canvas before you export a full set.

Pick the format for the content, not from habit

Three formats cover nearly every menu board, and the choice usually follows the content.

PNG uses lossless compression, so flat colour, sharp edges and small text stay clean. It is the safer choice for a text-heavy price panel, a logo or a layout with hard boundaries. Files are larger than a comparable JPG.

JPG compresses photographs efficiently and is a sensible choice when a board is dominated by food photography. Compression artefacts tend to show around high-contrast type, so avoid heavy compression on panels where prices sit against flat backgrounds.

MP4 is for motion. H.264 is the widely accepted codec: Xenial's content guidelines, for instance, ask for H.264 with a 5 Mbps target bit rate and 30 fps for full-screen video. Treat those as that vendor's numbers and check yours.

A practical note on transparency: PNG supports an alpha channel, but video often does not in a signage pipeline. Xenial's documentation states that videos with a transparent background are not supported. If you need a see-through effect over a background layer, verify support before building the asset.

Match the canvas to the screen

A screen file has no bleed, no trim and no meaningful DPI. What matters is pixel dimensions and orientation.

These are the common configurations, not requirements. Confirm the native resolution of your display and the canvas your software expects; a mismatch is a routine cause of a board that looks stretched, letter-boxed or soft.

A portrait board should be designed vertically at portrait dimensions, with the panel mounted rotated. Rotating a landscape design at playback is what produces awkward crops and shrunken type.

Example canvases, not a requirement that every screen use these dimensions.

Leave a margin for overscan

Some displays crop slightly at the edges. Keeping essential content inside a margin is cheap insurance, and it is why many guidelines allow a percentage inset around the canvas.

Keep prices, item names and any required notices comfortably inside that margin, and let backgrounds run to the edge. If a price sits three pixels from the border, some screen somewhere will clip it.

Drop print habits before exporting

Most menu artwork is made in design tools built for print, and the defaults cause recurring problems.

• Export in RGB, not CMYK. Screens are RGB, and a CMYK file can shift colour or be rejected outright.
• Stop thinking in DPI. The pixel dimensions decide sharpness. A 300 DPI export at the wrong pixel size is still wrong.
• Remove bleed and crop marks. The canvas is the screen, edge to edge.
• Keep source photography high quality. A small web image pulled from a site will look fine on a laptop and mushy across a large panel.
• Watch file size. Very large files make players work harder for no visible benefit. Menuboard Manager, for example, advises against pushing bit rates higher than recommended because file size doubles with no visible gain.

If fonts matter to the design, check whether your system needs the font file uploaded or the text rendered into the image. Relying on whatever font happens to be installed on a player is how a carefully set menu turns into a substitute typeface.

Test one file before exporting the set

Build one panel end to end and prove it on the real screen before producing twenty.

1. Export at the canvas your software specifies, in the format it accepts.
2. Load it on the actual player and display it full-screen.
3. Check the edges for cropping and the whole frame for stretching.
4. Read the smallest price from the customer position, and confirm the type is sharp rather than blurred by scaling.
5. For video, watch a full loop for stutter and confirm the transition back to the start is clean.

Then record the settings that worked: format, dimensions, colour mode, quality or bit rate, and frame rate. A short export recipe saves every future revision from repeating this. It also makes the file-handling question easier when you compare menu board software or work from a template, because you already know what your screens need.

Frequently asked questions

Is a PDF suitable for a menu board?

Usually not as the playback file. Some systems accept documents through a widget, but a still image or video exported at screen dimensions is more predictable. Check what your player accepts.

Should I export everything at 4K to be safe?

No. A 1080p screen cannot show more than its native resolution, so a 4K file is scaled down and costs bandwidth and decoding effort. Export 4K when the display is genuinely 4K.

Is an animated GIF an acceptable alternative to video?

It is usually the worse option. A short H.264 MP4 is typically smaller and cleaner than an equivalent GIF loop. Confirm your player's supported formats first.

Can I use a Canva export directly?

Often yes, provided you start the design at the correct pixel dimensions and export a format your system accepts. The canvas size matters more than the tool.

Export once, correctly

The right digital menu board file format is the one your player accepts, at the pixel dimensions of the screen, using a container suited to the content. PNG for crisp text, JPG for photography, MP4 for motion, RGB throughout.

Prove one panel on the real screen, write down the settings, then produce the rest. If you are setting up new screens with MenuPi, confirm the required canvas and formats for your specific displays before building the full set.