Industries

Understand the image URL before setting vehicle photo specs

A vehicle photo can look soft on a detail page even when a larger version exists upstream. One possible explanation sits inside the image address: a CDN path segment can act as a resize directive, requesting a particular rendition rather than identifying only the underlying photograph. Understanding that distinction helps a dealership ask better questions about photo quality before requesting another shoot or changing its upload process.

If search work is part of the scope, our website rule applies. We only do SEO on a site we built.

Separate upload requirements from delivered image dimensions

A useful investigation of DealerCenter photo requirements separates three things: the source file, the rendition requested through an image URL, and the space that rendition occupies on the website. Those are related, but they are not interchangeable. A source file might contain enough detail for a large display while the page requests a smaller rendition. Conversely, requesting a larger rendition cannot restore detail that the source photograph never contained.

This page explains how to reason about that delivery chain; it is not an official list of accepted file sizes or upload limits. Exact platform constraints need confirmation against current documentation or the relevant account workflow. Keep those verified constraints separate from the website's own presentation specification. Otherwise, an internal preference for a particular gallery shape can accidentally become an unsupported claim about what the platform requires.

Read a resize segment as an instruction

An image address may combine several jobs: identifying the image service, locating an asset, and asking the service to transform it. When a path segment acts as a resize directive, it affects the rendition delivered to the browser. It should not automatically be treated as part of the photograph's permanent identity. The practical question is which pieces locate the asset and which pieces control its presentation.

Verify the syntax before changing a path

Do not guess a replacement segment from its appearance. Confirm the supported transformation syntax and permitted usage through an appropriate technical source or a controlled inspection of the integration. A path that resembles a dimension could have additional meaning. Removing it might return a different rendition, produce an error, or violate an integration assumption. The implementation needs a documented rule rather than a string replacement that happens to work on one photograph.

For example, suppose a listing card and a gallery both receive the same small rendition. Enlarging the gallery container would not establish that the browser has received a more detailed image. The investigation should compare the requested resource with the displayed size and the available source.

Keep transformation logic in one place

A proposed integration should centralize any verified rendition rules. If each page template independently edits image addresses, future changes become harder to audit. A shared image-handling function can distinguish asset references from approved transformations and provide an explicit fallback when an address does not match the expected structure. The rule should preserve meaningful identifiers rather than broadly rewriting every path segment that contains digits.

Write specifications for the places photos appear

Start with the actual display roles: inventory card, main vehicle image, gallery view, and any enlarged presentation included in the proposed website. Record the intended container shape, expected display size, and whether the image should fit within the frame or fill it through cropping. These decisions explain what rendition the website needs. They also make it possible to assess whether a source file is suitable without inventing a universal minimum.

• For inventory cards, define a consistent frame and decide how much cropping is acceptable when source photographs have different proportions.
• For the main vehicle image, prioritize a complete and understandable view of the vehicle over a crop chosen only to fill empty space.
• For an enlarged gallery, verify that the delivered rendition supports the intended viewing size and that its source contains useful detail.

Aspect ratio and resolution solve different problems. Aspect ratio describes shape; resolution describes the available pixel dimensions. A high-resolution photograph can still crop poorly inside a narrow card. A correctly shaped photograph can still appear soft when stretched. The specification should address both, then include a review of representative exterior, interior, portrait-oriented, and unusually framed images if those occur in the inventory source.

Treat cropping as a merchandising decision

Automatic center cropping can remove information that matters to a shopper. A wide vehicle photograph may lose part of the front or rear when placed inside a different frame. An interior photograph may lose the feature it was intended to show. Decide where consistency is worth that tradeoff and where fitting the whole image is preferable. The correct choice depends on the display role rather than a blanket preference for edge-to-edge imagery.

Photo order deserves its own rule. Preserve an intentional source sequence when the feed provides one and the dealership approves its meaning. If ordering data is absent or inconsistent, define the fallback explicitly. Do not assume a filename identifies the preferred lead photograph. A predictable gallery should also handle a missing first image without leaving the shopper on an empty frame while other usable photos remain available.

Trace the image from feed reference to browser

When diagnosing an issue, capture the original image reference received by the website, any transformation applied by the integration, and the resource ultimately requested by the browser. Compare those with the rendered image dimensions. This creates a concrete chain of evidence. It can distinguish a source-quality problem from an incorrect rendition request, an unintended crop, or a display rule that stretches the image beyond its useful size.

Check updates as well as first loads

A photo replacement introduces another question: how does the website recognize that an asset has changed? Review whether the feed reference changes, whether the image service retains the same address, and how the integration handles caching. Do not assume that a refreshed feed necessarily means a browser receives a refreshed image. Test the observed update path and document the supported behavior before promising immediate replacement everywhere.

Failure states should be deliberate. A missing or rejected image request should produce a clear fallback rather than a broken icon or a misleading photograph from another vehicle. Gallery controls should remain usable when only one photo exists. Alternative text should describe the image appropriately without inventing vehicle features that are not visible or supported by listing data. These checks belong alongside rendition quality because shoppers encounter the complete gallery experience.

Ask for an image specification you can verify

A useful specification separates verified platform constraints, source-photo guidance, transformation rules, and website display choices. It identifies the evidence behind each rule and includes representative checks. When comparing a proposed website engagement, ask how the partner will inspect image delivery and document any URL assumptions. That gives the dealership a concrete basis for approval without accepting unsupported upload limits or a promise that changing one path segment will fix every photo problem.