Real Estate Image Optimization

Multiple Listing Services (MLS) across North America each set their own image specifications, but most share common requirements that agents and photographers need to follow.

The majority of MLS platforms require listing photos to be:

• Minimum 1024x768 pixels, with many now requiring 1920x1080 or larger
• JPEG format (some newer systems accept WebP or PNG)
• Under 5-10 MB per file depending on the MLS
• Landscape orientation for primary listing photos
• RGB color space (not CMYK, which is intended for print)

Bright MLS, one of the largest in the US, requires a minimum of 1024x768 and recommends 2048x1536 for optimal display. Stellar MLS requires photos to be at least 640x480 and no larger than 15 MB. CRMLS, the largest MLS in the US, accepts files up to 10 MB with a minimum dimension of 1024 pixels on the longest side.

To meet these requirements efficiently, establish a batch processing workflow using tools like ImageMagick, Sirv, or Adobe Lightroom's export presets. Create a master export at 3000x2000 (which satisfies even the strictest MLS requirements) at JPEG quality 85, then generate web-optimized derivatives at quality 75-80 for your website. This dual-export approach ensures MLS compliance while keeping your site fast. Always verify your images meet your specific MLS requirements before uploading, as rejected uploads waste time during critical listing periods.

Virtual tours have become essential in real estate marketing, with NAR reporting that listings with virtual tours receive 87% more views than those without. However, 360° panoramic images and virtual tour assets present unique optimization challenges due to their large dimensions and file sizes.

A single equirectangular panorama typically starts at 8000x4000 pixels or larger, resulting in files of 15-30 MB before any optimization. To make virtual tours web-performant:

• Tile your panoramas — Rather than loading one massive image, split each 360° view into a cube map (6 faces) or tile grid. Viewers like Marzipano and Pannellum load only visible tiles, dramatically reducing initial load time.
• Use multiple resolution levels — Generate 3-4 quality tiers per panorama. Load low-resolution tiles first (256x256), then swap in high-resolution tiles (512x512) as the user explores.
• Target 2-4 MB per panorama after optimization for a balance between quality and performance. JPEG quality 72-78 works well for most interior panoramas.
• Preload the first view — Whatever direction the camera faces when the tour loads, ensure those tiles are prioritized via preload hints or priority fetch.

For Matterport, iGuide, and similar platforms, you have less control over image delivery since the platform handles it. Focus instead on the source capture quality — shoot in the highest resolution your camera supports and let the platform's pipeline handle optimization. For self-hosted tours using Three.js or A-Frame, implement progressive loading with a low-resolution placeholder texture that updates as tiles stream in. This keeps your Largest Contentful Paint (LCP) fast while delivering a rich experience.

Drone photography has transformed real estate marketing by providing perspectives that showcase properties, lots, and neighborhoods in ways traditional ground-level photography cannot. However, aerial images come with specific optimization considerations.

Modern drones like the DJI Mini 4 Pro capture images at 48 MP (8064x6048 pixels), producing RAW files exceeding 50 MB. Even JPEGs straight from the drone are typically 12-20 MB — far too large for web use without processing.

Recommended drone image workflow:

• Capture in RAW+JPEG if your drone supports it. Use RAW for editing and the JPEG as a quick reference.
• Edit in Lightroom or Capture One with lens correction profiles applied (most popular drones have profiles built in).
• Export at 3000x2000 for archival and MLS upload (JPEG quality 85-90).
• Generate web derivatives at 1920x1080 (quality 72-78) for listing detail pages.
• Create 800x450 thumbnails (quality 70) for gallery grids and search results.

Aerial shots can tolerate more compression than interior detail shots because they contain broader tonal gradients and less fine texture. You can safely use JPEG quality 65-72 for web delivery without noticeable artifacts, saving 30-50% file size compared to interior shots compressed at the same perceptual quality.

Technical tip: Drone images often contain extensive EXIF and XMP metadata including GPS coordinates, flight altitude, gimbal angle, and camera settings. Always strip GPS data before publishing if the exact location is sensitive. Tools like ExifTool or Sirv's auto-strip feature handle this in batch.

Agent headshots appear across every touchpoint in real estate — listing pages, search results, business cards, email signatures, social profiles, and yard signs. A single headshot may need to be delivered at a dozen different sizes, making responsive optimization critical.

Recommended headshot specifications:

• Master file: 2000x2000 pixels minimum, shot against a neutral background, JPEG quality 90 or PNG for transparent background variants.
• Listing pages: 400x400 or 300x300, JPEG quality 78-82. These appear alongside listing details and should load quickly without dominating bandwidth.
• Search results: 150x150 or 100x100 thumbnails, JPEG quality 72-75.
• Social media: 1080x1080 for Instagram, 800x800 for LinkedIn, 500x500 for Twitter/X.

For team pages featuring 10-30 headshots, optimization becomes critical. An unoptimized team page can easily weigh 15-25 MB. Best practices include:

• Use CSS aspect-ratio or explicit width and height attributes to prevent layout shift as images load.
• Implement native lazy loading with loading="lazy" for all headshots below the fold.
• Serve WebP with element fallback — WebP headshots are typically 30-40% smaller than equivalent JPEGs.
• Consider using a CDN with on-the-fly resizing (Sirv, Cloudinary, Imgix) so you upload one master headshot and request any size via URL parameters.

Color accuracy matters for headshots — clients and agents want natural skin tones. Always work in sRGB color space for web delivery, and test your compression levels to ensure skin tones don't shift or band at your chosen quality setting.

Floor plans bridge the gap between photography and technical documentation. They help buyers understand spatial relationships, room dimensions, and property flow in ways that photos alone cannot. Optimizing floor plans requires a different approach than photographic images.

Key considerations for floor plan optimization:

• Vector vs. raster: If your floor plans are created digitally (in tools like RoomSketcher, Floorplanner, or AutoCAD), export as SVG for web use. SVG floor plans are resolution-independent, searchable, and typically 50-80% smaller than raster equivalents. They also remain sharp when users zoom in to read dimensions.
• Raster floor plans: When SVG isn't available (photographed or scanned plans), use PNG format to preserve the sharp lines and text. JPEG compression creates artifacts around text and line edges that make floor plans hard to read.
• Recommended raster size: 2000x1500 for detail views, 800x600 for thumbnails. PNG-8 with 256 colors works well for simple floor plans and is significantly smaller than PNG-24.

Interactive floor plans are becoming standard on premium listing sites. These overlay clickable hotspots on the floor plan that link to photos of each room. For these implementations:

• Use an SVG base layer for the floor plan with elements wrapping each room area.
• Lazy load the room photos that appear on click or hover.
• Keep the base SVG under 100 KB by simplifying paths and removing unnecessary metadata.

Property maps showing lot boundaries, nearby amenities, and neighborhood context perform best as interactive map embeds (Google Maps, Mapbox) rather than static images. If you must use static maps, capture at 2x resolution for Retina displays and serve responsive sizes via srcset.