Blog Technical 7 min read

JPEG Placeholder URLs for Email and Social Crawlers

Social crawlers and email clients reject SVG images. Use JPEG placeholder URLs to ensure og:image previews and newsletter banners render in every client.

jpeg placeholder imageemail imagesog imagesocial crawlersnewsletter images
JPEG Placeholder URLs for Email and Social Crawlers

SVG is the most efficient format for web placeholders, but it is broadly rejected by email clients and inconsistently supported by social preview crawlers. JPEG is the safe format for any image that leaves the browser — og:image tags, newsletter hero banners, and transactional email product photos all need raster.

fallback.pics generates JPEG output from the same URL pattern as SVG, with just a format extension change. Switching an SVG email placeholder to JPEG is a one-character change in the URL, and the cached JPEG is served from the CDN on every subsequent request.

Why SVG fails in email

Email clients strip or ignore SVG images

Email HTML is rendered by one of several different rendering engines, including WebKit (Apple Mail), Trident or Word (Outlook on Windows), Blink (Gmail web), and proprietary engines in mobile mail apps. None of these environments reliably render SVG in img tags, and several strip SVG entirely.

Outlook 2016–2021 on Windows uses the Word rendering engine, which does not support SVG at all. Gmail on the web strips SVG img tags from emails for security reasons. Apple Mail renders SVG but scales it to 0×0 in some configurations. The safest rule is: never use SVG in email HTML.

When you use fallback.pics in email templates and forget to add the .jpg extension, the default SVG response renders as a broken image in roughly half of all email clients. The fix is always to specify the format explicitly.

Social crawlers

Facebook, LinkedIn, and Twitter OG image requirements

Social platforms crawl og:image URLs when a link is shared. The crawler fetches the image, processes it, and stores a raster copy for the link preview card. Facebook and LinkedIn require JPEG or PNG; they reject SVG og:image URLs entirely.

Twitter (X) accepts some SVG URLs from certain CDNs but processes them inconsistently. For reliable social preview cards, use JPEG at 1200×630 pixels. This size is the recommended Open Graph image size used by all major platforms.

Pinterest, Discord, and Slack also crawl og:image. Discord renders link previews using an internal image proxy that requests and caches a raster copy. SVG URLs in og:image will produce either a broken preview or a distorted render depending on the platform's proxy behavior.

JPEG format request

Requesting JPEG from fallback.pics

Append .jpg or .jpeg to the dimension segment to request JPEG output. The generated image uses the same colors, text, and layout as the default SVG, encoded as a standard JPEG. No other URL parameters need to change.

For Open Graph placeholder images specifically, use 1200×630 with a JPEG extension. Keep the background color dark enough to create contrast with the white or light text label. A purple or dark-gray background produces readable og:image previews on all major social platforms.

Implementation text
<!-- SVG (web only — do not use in email or og:image) -->
<img src="https://fallback.pics/api/v1/800x600/7C3AED/FFFFFF?text=Hero" />

<!-- JPEG for og:image meta tag -->
<meta
  property="og:image"
  content="https://fallback.pics/api/v1/1200x630.jpg/7C3AED/FFFFFF?text=Blog+Post"
/>
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
<meta property="og:image:type" content="image/jpeg" />

<!-- JPEG for email newsletter banner -->
<img
  src="https://fallback.pics/api/v1/600x200.jpg/18181B/FFFFFF?text=Monthly+Update"
  width="600"
  height="200"
  alt="Newsletter banner"
  style="display:block; border:0; outline:none;"
/>

File size

JPEG compression settings for placeholder images

JPEG compression is lossy. For placeholder images, the quality setting has almost no visible impact because the content is simple: flat colors, geometric shapes, and a short text label. A quality of 70–80 is sufficient and keeps file sizes small.

A 1200×630 JPEG placeholder at quality 75 is typically 18–25KB. The same image as PNG is 60–90KB. For social preview images where file size affects cache fill times and bandwidth for mobile social app users, JPEG is clearly the right choice.

Email testing

Verify JPEG placeholder rendering across email clients

Use Litmus or Email on Acid to test placeholder image rendering across client combinations before sending a campaign. These tools render a copy of your email in over 100 client and device combinations and show screenshots of the result.

Pay particular attention to Outlook on Windows (Word rendering engine), Gmail on Android, and dark mode in Apple Mail. Outlook does not respect CSS max-width on images, so always set explicit width attributes. Gmail on Android sometimes clips images wider than the screen; test at 320px and 375px viewport widths.

Keep email placeholder images below 100KB per image. Many email clients and mobile networks cache aggressively, and large images slow down email open time. For transactional emails, 600px wide JPEG placeholders at quality 75 stay well under that threshold.

OG image testing

Validate og:image JPEG placeholders with social debuggers

Facebook's Sharing Debugger at developers.facebook.com/tools/debug lets you paste a URL and see exactly how the crawler fetches and renders your og:image. Use it after deploying placeholder URLs to confirm the JPEG is being picked up correctly.

LinkedIn's Post Inspector at linkedin.com/post-inspector, Twitter's Card Validator (now X), and OpenGraph.xyz all provide similar validation. Run each one when you first set up a JPEG placeholder workflow to verify the format, dimensions, and cache headers are correct.

Implementation text
# API docs
https://fallback.pics/docs/
https://fallback.pics/placeholder-image-api/

# Related posts
https://fallback.pics/blog/og-image-placeholders-blogs-docs-social-sharing/
https://fallback.pics/blog/png-vs-svg-placeholders-production/

Key takeaways

What to standardize before shipping

  • Never use SVG in email HTML — use JPEG or PNG for all newsletter and transactional email images.
  • Facebook, LinkedIn, and Pinterest require raster og:image; use JPEG at 1200×630 for social preview placeholders.
  • Append .jpg to the dimension segment in fallback.pics URLs to request JPEG output — no other changes needed.
  • JPEG at quality 75 produces 18–25KB for a 1200×630 placeholder; PNG at the same size is 3–5× larger.
  • Validate og:image JPEG placeholders using Facebook's Sharing Debugger and LinkedIn Post Inspector before launch.

Production fallback layer

Use fallback.pics anywhere an image URL is accepted.

Start with one deterministic URL and standardize fallback behavior across your design system.

Read the docs