PDF Menus to JPG for Restaurant Social Stories

TL;DR: Convert only the menu pages you will post into sharp JPGs, crop to story-safe focal areas, and keep the master PDF for print updates. Social apps prefer images; kitchens still own the PDF.

Why the full PDF fails in Stories

Instagram, TikTok, and Facebook Stories expect vertical images, not multi-page documents. Uploading a PDF link loses impulse viewers. A page rasterized to JPG lets you swipe through brunch, dinner, and drinks as separate frames with readable prices.

A quick pass through a PDF to image converter beats screenshotting a zoomed viewer on a laptop—screenshots smear type and clip margins inconsistently.

Export only the pages you will actually post

Seasonal inserts, allergen matrices, and wine lists may live in the same PDF. Convert the guest-facing pages first. Naming files brunch-p1.jpg, brunch-p2.jpg keeps the social calendar sane when the chef swaps a special.

Skip: internal cost sheets accidentally bound into the export packet
Keep: cover art if it carries brand color for the first story frame
Split: dense dual-column pages into two crops rather than one illegible frame

Resolution that survives compression

Social networks recompress aggressively. Start from a crisp raster—roughly 150–200 DPI equivalent for letter-size menus is a practical band for phone viewing. Ultra-high DPI creates huge uploads without surviving the network’s second squeeze. If prices look soft after upload, increase source sharpness before you blame the app.

Prefer JPG for photographic menu covers; PNG can help for flat graphic menus with hard-edged logos, but JPG usually wins for photo-heavy hospitality PDFs.

Crop for vertical safe zones

Story UI eats the top and bottom. After conversion, open the JPG and crop so dish names and prices sit in the middle third. Do not rely on viewers to pinch-zoom a full letter page in a nine-by-sixteen frame.

For two-column menus, make two story frames: left column, then right. Captions can say “Dinner — sides” so the sequence is obvious.

Price accuracy and version control

Never edit prices only on the social JPG while the PDF lags. Change the PDF (or design file), re-export images, then schedule posts. Stamp a quiet version date in the filename: dinner-2026-11-01-p2.jpg. When a guest argues a Story price, you can prove which file was live.

Allergen and alcohol caveats

If legal notes live in six-point type at the PDF footer, they may vanish in a crop. Either keep a dedicated story frame for disclaimers or point to the full menu URL in the caption. Fancy crops are not an excuse to hide required notices.

Team workflow for multi-location brands

Central marketing converts the approved PDF; local managers only schedule the issued JPGs. Locals should not re-screenshot older PDFs from email. A shared folder with “current” and “archive” subfolders prevents last month’s oyster price from resurfacing.

Accessibility in captions

Images of text are weaker for screen readers. Add alt text where the platform allows and repeat key dish names in the caption. Unicode-heavy decorative PDF fonts may rasterize finely yet still need plain-language captions for clarity.

When a single hero dish beats the full page

Sometimes convert the PDF page, then crop one signature plate for the cover story and link “full menu” in bio. Full-page readability still matters for the swipe-through; the hero crop is bait, not a replacement for priced pages.

Whenever the PDF updates, run the new pages through freepdftoimg.com, replace the dated JPGs, and retire yesterday’s files from the scheduler.

Translator and multi-language menus

If you maintain English and second-language PDFs, convert each language set into its own dated folder. Do not crop an English price panel onto a translated story frame. Guests notice mismatches instantly, and so do inspectors when alcohol or allergen text differs by language.

QR codes in the PDF

QR targets often sit in corners that story crops destroy. After conversion, either keep a full-page frame that includes the code or place the ordering URL in the caption and bio. A half-cropped QR is worse than no QR.

Influencer kits and dark kitchens

When sending assets to creators, ship the JPG set plus a one-line “prices as of DATE; PDF is canonical.” Creators screenshot anyway; giving them clean rasters reduces the chance they post a three-month-old PDF page from an old email.

Delivery app thumbnail traps

Delivery platforms often want square heroes, not story verticals. Convert the PDF cover or a plated special to a separate square JPG rather than stretching a story crop. Keep a small kit: story verticals for owned social, square for apps, PDF for print. One export preset cannot serve every aspect ratio without someone getting blurry prices.

Never upscale a soft screenshot to fake resolution; re-export from the PDF at the size you need.

Pre-post checklist

Correct PDF version, only guest pages converted, vertical crops checked on a phone, disclaimers preserved or captioned, filenames dated, archive moved. Menus sell better as stories when the type stays sharp and the source of truth stays the PDF. If a story frame needs a price correction, fix the PDF first—never permanent-marker the JPG as your new master.