Document Workflows: Convert Word and Excel to JPG for Signage

It is Thursday afternoon. The new menu launches Friday morning at all 14 quick-service locations. The marketing director sent the menu as a Word document. The signage CMS only accepts JPG. The franchise owners are texting you because the prices in their location's display do not match the new menu. You have six hours to convert, distribute, and verify across 14 displays before the morning rush. This is the workflow that turns that scramble into a 20-minute task you can repeat every week.

The print shop tells you they need a JPG. You hand them the original Word document. They re-render it on their system, the fonts shift, the layout breaks, and the menu board you needed by Friday is wrong. Digital signage kiosks, retail price displays, and print shops all prefer flat raster images over editable documents. JPG is the universal currency. This guide walks through the workflow that produces signage-ready JPGs every time, with the resolution math, color-space settings, and CMS-compatible compression that ship a perfect menu update in under 10 minutes per location.

Background: why DOCX and XLSX fail at the destination

A DOCX file is not actually a finished document. It is instructions for assembling a document. The instructions reference fonts, rely on a particular Word version's rendering engine, and assume the destination has the same printer driver, page margins, and language settings. The signage player, the print shop, or the kiosk operator may have none of those.

A JPG eliminates every variable. It is a snapshot of the document at the exact moment you exported it. Fonts are rasterized, layout is locked, colors are committed. The receiving system has zero opportunity to "interpret" the file differently.

Why JPG, not the source file

A DOCX or XLSX file is editable, which means its appearance depends on the fonts installed on the rendering machine. Your print shop probably does not have your custom corporate font. Their LibreOffice substitution makes Times look like Liberation Serif, your bold sub-heads turn regular weight, and tables shift columns. A JPG bypasses all of that. It is a snapshot of the document as you saw it, frozen at the moment of export.

Digital signage players (BrightSign, Yodeck, Screenly, ScreenCloud) accept JPG natively and play it back without rendering quirks. Many of them accept DOCX too, but the rendering on the player is even less predictable than at the print shop.

Step-by-step: from DOCX to displayed JPG

1. Design at the destination aspect ratio. Use the aspect ratio calculator to size Word page at 16:9 (13.33x7.5 inches) for landscape TVs.
2. Embed fonts in the source. File > Options > Save > Embed fonts in the file. Protects against rendering on machines without the font.
3. Export to PDF. File > Export > Create PDF. This freezes layout and fonts.
4. Convert PDF to JPG. Use the PDF to JPG converter at the resolution your display needs.
5. Verify dimensions. Open in the image info tool and confirm pixel count matches display native resolution.
6. Compress for upload. If your CMS caps at 10 MB, run through the JPG compressor to land under cap.
7. Upload to CMS and assign to displays. Schedule the playback window.
8. Verify on at least one physical display. Glance at it before the customer-facing rollout.

The basic conversion path

From Microsoft Word, export the document as PDF first, then convert the PDF to JPG. Direct DOCX-to-JPG converters exist but introduce font substitution risk; the PDF intermediate step preserves the rendering exactly as you saw it on screen.

From the PDF, generate page-by-page JPGs using the PDF to JPG converter. For multi-page menus or signage decks, you end up with menu_p1.jpg, menu_p2.jpg, and so on. Most signage systems prefer one image per slide.

Excel to JPG: the table problem

Excel-to-JPG is harder because spreadsheets do not have a natural "page" the way documents do. The reliable workflow: in Excel, select the cell range you want as an image, set print area to that selection, set page setup to fit-to-one-page, print to PDF, then convert the PDF to JPG. The result is a single image of just the data you wanted, sized to a known aspect ratio.

For weekly price lists, build a template once with the print area locked and a macro that prints to PDF and triggers the JPG conversion. Updating next week becomes a single click instead of a 10-step re-do.

Embedded fonts and the substitution risk

Even after exporting to PDF, fonts can still substitute on the destination machine if they were not embedded in the export. Verify "embed all fonts" is enabled in your PDF export settings. Acrobat's File > Properties > Fonts tab shows which fonts are embedded and which are referenced. Replace any "type 3" or "no embed" entries before sending to print.

Resolution for signage vs print

Digital signage TVs are 1080p (1,920 by 1,080) or 4K (3,840 by 2,160). Export at the native resolution of the display. Anything more is wasted, anything less looks soft. For a 4K menu board, render the PDF to JPG at 300 ppi for an 11x17 source page, which produces 3,300x5,100 pixels, more than enough for crisp 4K display.

For print signage like A2 posters or A0 trade-show graphics, the math is different. A0 is roughly 33x47 inches; at 150 ppi viewing distance for a poster, you need 4,950x7,050 pixels. That requires the source PDF to be 600 ppi at A4 size or 300 ppi at A2. Set the conversion accordingly. Use the DPI converter to verify the final file before sending to print.

Display aspect ratio comparison

Display type	Aspect ratio	Common resolution	Source page size
1080p TV (landscape)	16:9	1920x1080	13.33x7.5 in
4K TV (landscape)	16:9	3840x2160	13.33x7.5 in @ 300 ppi
Portrait kiosk	9:16	1080x1920	7.5x13.33 in
Ultrawide menu strip	21:9	3440x1440	17.2x7.2 in
Square social display	1:1	1080x1080	9x9 in
A2 print poster	1:1.41	4961x7016 @ 300dpi	16.5x23.4 in
Trade-show banner	varies	3000x6000+ typical	per print shop spec

Color: sRGB for screens, CMYK for offset print

Digital signage is always sRGB. Print shops vary. Most small-format and digital print is sRGB; offset and large-format may want CMYK. Ask before exporting. If the shop says sRGB, set your PDF export and JPG conversion both to sRGB. If they say CMYK, export PDF as PDF/X-1a with CMYK conversion and provide the PDF directly. Converting CMYK to JPG produces unpredictable color shifts at every step.

Compression for upload to signage CMS

Signage content management systems (Yodeck, ScreenCloud, Rise Vision) usually accept JPG up to 10 MB. A 4K JPG at quality 95 lands around 4 to 8 MB. Comfortably under the cap, but if your CMS is slower than your patience, run the file through the JPG compressor at quality 85 and drop it to 1 to 2 MB without visible difference on a TV viewed from 6 feet away.

Variable data: per-location signage at scale

Chains with 50+ locations need different prices, addresses, and promos per store. Manually generating 50 unique JPGs per week is unsustainable. The scaling solution is variable-data publishing: a master template with placeholder fields, a CSV with per-location data, and an automated script that generates one JPG per row. Adobe InDesign's Data Merge handles this; for web-based workflows, headless Chrome rendering a templated HTML page works equally well.

The setup cost is half a day; the ongoing cost is a single command-line invocation per weekly update. The ROI lands in week three.

Refresh cadence: how often to update

Static signage should refresh content at least monthly to avoid blindness. Customers stop seeing signage that has not changed in 90 days. Daily-changing content (specials, hours, weather) keeps the displays engaging. Weekly refreshes on menus and promos balance freshness against production effort.

Time-of-day rotation extends single-image content by varying what plays during breakfast, lunch, and dinner. The same physical display becomes three different signage slots without three different files.

Font choice and text legibility on emissive displays

Fonts that read well in print do not always read well on emissive displays. Thin weights (Helvetica Light, Inter Thin) shimmer and lose readability on 4K TVs viewed from across a room. Use medium weights or heavier for body text, and reserve thin weights for large display sizes only. Sans-serif faces (Inter, SF Pro, Roboto) outperform serif faces (Times, Georgia) for signage at typical viewing distances.

Test legibility from the expected viewing distance before deploying. If you cannot read the display from 6 feet, your customers cannot either. The 30-second test prevents weeks of poor-performing signage.

Real-world signage examples

Restaurant menu update. Edit DOCX template in Word, export PDF, convert to JPG with the PDF to JPG converter at 1,920x1,080, upload to Yodeck. Total time after the template is built: 4 minutes per update. The 14-location chain runs this every Monday morning.

Retail price list at a hardware store. Update XLSX, set print area, export PDF, convert to JPG, replace previous image in ScreenCloud. Done weekly in under 10 minutes by the assistant manager. Eliminated a 2-hour task that previously went through a graphic designer.

Trade-show banner for a tech startup. Design in Word at A2 with print-shop bleed, export PDF at 300 ppi, convert to JPG, email to print shop. Same file works for both the printed banner and a JPG slot on the booth's video wall.

Day-of-week and time-of-day scheduling

Modern signage CMSs let you schedule different JPGs for different days and times. Coffee shops schedule breakfast menu 7-11 AM, lunch menu 11-2, all-day specials after 2 PM. Restaurants split dinner menu by reservation window. The single physical display serves multiple use cases without intervention.

Common signage mistakes

1. Tiny fonts that look fine on screen and disappear on a TV from 8 feet away. Minimum body text size on a 1080p screen is 36 pt at a 6-foot viewing distance.
2. Pure white backgrounds. They glare on emissive displays. Soft off-white (245,245,245) reads better and reduces eye fatigue.
3. JPEG artifacts on solid color blocks. Keep quality 90 or higher for clean edges on logos and text.
4. Wrong aspect ratio. Use the aspect ratio calculator before designing, not after.
5. Tiny logos or pricing. Viewing distance triples the minimum legible size compared to letter-size printed documents.
6. Animation expected, static delivered. If the CMS supports video, MP4 may be the better format. JPG is for truly static content.

Advanced tips for repeatable signage workflows

• Template every recurring layout. A "weekly menu" Word template with print area locked drops update time from 30 min to 4 min.
• Version your filenames. menu_2026-05-19.jpg sorts chronologically and prevents the "which file is current?" question.
• Pre-flight on a TV. Send to your home TV (or office display) before pushing to all locations. Catches font and color issues.
• Maintain a brand asset library. Logos, color palette, font files in a shared folder. Use the color palette tool to pull brand colors from existing assets.
• Schedule playback transitions. Signage CMSs can auto-rotate JPGs on a schedule. Set lunch menu vs dinner menu transitions once.
• Use vector source when possible. If your menu is in InDesign or Illustrator, export PDF then JPG. Crisper text than a Word-to-JPG path.
• Compress with awareness of compression bands. Quality 85 is the sweet spot for signage. Below 80 starts visible artifacts on solid backgrounds.

FAQ

Can I use Google Docs instead of Word?

Yes. Export Google Docs as PDF, then convert PDF to JPG. The same intermediate-PDF step preserves layout exactly.

What about PowerPoint for signage?

PowerPoint is excellent for signage because you can design at exact display dimensions. Export each slide as JPG (File > Export > Change File Type > JPEG). PowerPoint also supports direct export at native display resolution.

My signage CMS supports PDF, why bother with JPG?

PDF playback on signage players is inconsistent. Some players render fonts incorrectly, some respect bleeds when they should not. JPG eliminates the variables. Use PDF only if the CMS explicitly recommends it.

How do I handle video alongside static JPGs?

Most signage CMSs support both. JPG for static content (menus, hours, promos), MP4 for animated content (commercials, demos). Schedule each separately.

What is the best free alternative to commercial signage CMSs?

Yodeck offers a free tier for 1 screen. Screenly OSE is open source, runs on Raspberry Pi. For very simple needs, a Chromecast with a slideshow web page works.

Should I include the price in the JPG or overlay it via the CMS?

Include it in the JPG. CMS overlays introduce another rendering inconsistency. One file, one source of truth.

How do I deal with multiple locations needing different versions?

Master template in DOCX with location-specific fields, batch-export PDFs (one per location), batch-convert to JPGs, upload by location group in the CMS. A scripted version of this runs in 5 minutes for 14 locations.

QR codes and dynamic content on static images

Add QR codes to static signage to bridge the digital and physical experience. A menu JPG with a QR code linking to nutritional information, online ordering, or a feedback form converts viewers into engaged customers. Generate the QR code once with the link encoded, embed in the Word source, export through the standard PDF-to-JPG pipeline. The QR code survives compression as long as you stay above quality 80.

Maintaining brand consistency across many locations

For chains with 10+ locations using the same signage CMS, brand consistency is enforced through a master template. The master is a PowerPoint or Word file with locked layouts, embedded fonts, and variable fields (location address, current promo, weekly menu). Local managers fill the variable fields, export to PDF, convert to JPG, upload. The brand-visible layout never drifts.

Compare this to letting each location design their own signage: within a month, font choices diverge, color values drift, and the brand erodes. The template+export pipeline is the corporate marketing version of CI/CD.

Animation versus static: when to upgrade

JPG is for truly static content. If your signage CMS supports video, MP4 enables transitions, motion graphics, and dwell-time engagement that static JPGs cannot match. The upgrade cost is real: video creation takes 5-10x longer than equivalent static design. The engagement uplift on right-context content (lunch traffic, retail dwell) is often worth it. For pricing menus and ops content, static JPG remains the right tool.

Sensor-aware signage

Modern CMSs (Yodeck Pro, ScreenCloud) integrate with people-counters and dwell-time sensors. Static content can be swapped contextually: lunch menu when traffic is high, slow-rotating gallery when the store is empty. JPG remains the format; the orchestration is the new capability.

Build the pipeline once

The first signage export takes an hour while you figure out the right resolution and color settings. The hundredth takes 4 minutes. Standardize on PDF as the intermediate format, the PDF to JPG converter for the final raster, and the JPG compressor for the CMS-upload variant, and your weekly signage update becomes a 10-minute job instead of a half-day project. Pair the workflow with the aspect ratio calculator for layout planning and the image info tool for final verification before publishing. For ultra-large-format trade-show graphics, the DPI converter sets the right print resolution metadata, and the JPG to PDF converter creates the print-shop-ready deliverable. See the tools directory for the complete signage kit.