Photo Resolution and File Size for Marketplace Uploads
Huge files stall posting. Tiny files look cheap. A dealer standard for photo resolution and file size for Marketplace uploads that survives phones, compression, and a busy queue.
The associate shot a perfect stall set. Then AutoPost sat on "failed" because the files never left the phone, or they left the phone as social-app screenshots that look like they were taken through a screen door. Photo resolution and file size for Marketplace uploads is not a photographer's debate. It is a posting-operations problem: too heavy and the workflow stalls; too light and the listing looks like a scam, a clone, or a wholesale flyer.
Meta does not publish a dealer-facing spec sheet that you should treat as a permanent rule, and those limits change. Check current Marketplace upload behavior in the product when you train staff. What you can standardize is your store's capture settings, how files move from camera to posting, and a quality bar that still looks sharp after Marketplace compression.
This article sets that bar: how to shoot so files survive compression, how to stop the two failure modes (giant camera-RAW dumps and tiny WhatsApp forwards), and how to keep every rep on the same pipeline.
What "Good Enough" Means After Compression
You do not control Marketplace's compression. You control the input.
The input test
A usable listing photo, after it has been through the platform:
- Body lines stay sharp at phone-zoom on a door handle or a badge.
- Mileage on a cluster shot remains readable.
- Wear close-ups still show texture, not a smear.
- The cover tile does not look pixelated or muddy next to competing listings.
If your original is a screenshot of a screenshot, no upload setting will save it. If your original is a 40-megapixel file with a 20-megabyte size, you may be fighting upload time, phone heat, and failed posts without gaining anything the buyer will see.
Resolution is not the same as sharpness
A huge, out-of-focus file is still a bad photo. A reasonably sized, in-focus, well-lit file survives compression better than a giant blurry one. Get focus and light right first. Then keep resolution in a practical band.
A Conservative Store Standard for Photo Resolution and File Size for Marketplace Uploads
Because platform limits change, treat the following as a conservative operating standard for dealership capture, not as Meta policy.
Capture on the phone
- Use the main camera, not the ultra-wide, for covers and flanks. Ultra-wide adds distortion and edge softness.
- Turn off "optimize storage" modes that replace originals with low-res cloud placeholders before you post.
- Avoid in-camera "HDR+" looks that smear badges if you have seen that on your device; test one car and inspect badges and cluster digits.
- Do not shoot in a professional RAW workflow unless someone on staff actually converts those files before posting. RAW dumps belong in an archive, not in a Marketplace queue.
A practical size band
Aim for files that are clearly larger than a social-story download and clearly smaller than a desktop-retouch original:
- Shoot at the phone's full standard JPEG (or HEIC, then export JPEG if your posting path needs JPEG).
- If you batch-resize, keep the long edge in a range that still looks sharp on a modern phone — large enough to crop slightly, not so large that ten photos choke a posting session.
- If a single photo is taking dramatically longer to upload than the others, it is probably an outlier (burst RAW, screenshot of a 4K video frame, or a file that never compressed). Replace it.
Do not quote a magic megapixel number as a Facebook rule. Train the behavior: original from the camera app, not from Messenger.
Aspect and crop
Shoot a little loose so a later crop still has resolution. Tight shots of a badge that are then cropped again become mush. Covers should still follow landscape vs portrait decisions; do not upscale a portrait to fake a landscape.
How Photo Resolution and File Size for Marketplace Uploads Get Ruined
Most "Marketplace looks bad" problems are not the platform. They are the path.
The Messenger / group-chat path
Reps text photos to themselves or to a "lot photos" group. Those apps recompress. What arrives is not what left the camera. Ban this path for listing images. Use the camera roll original, a shared drive that preserves originals, or a direct pick from the device at post time.
Screenshots of the DMS or of another listing
Screenshotting a website photo — including your own dealer site — produces a low-resolution, sometimes watermarked image that may also be a stock or catalog problem. Shoot the car.
Email and desktop round-trips
Email clients shrink attachments. If a manager "just emails the set to the internet guy," you may have already lost the resolution you paid for in the stall. Use a transfer method that does not auto-downsize.
Video frames as stills
A freeze-frame from a walkaround video is convenient and usually soft. If you need a still, take a still.
Aggressive editing
Heavy sharpening before upload plus platform sharpening equals halos. Heavy noise reduction on a night shot plus compression equals plastic paint. Edit gently: straightening, modest exposure, crop. Then stop.
A Pipeline You Can Audit on Monday Morning
Stall
- Phone storage is not full (full storage is how phones silently save low-res).
- Lens is clean.
- Camera app, not Instagram, not Snapchat, not Messenger camera.
- Review sharpness on the badge and on the cluster before leaving the car.
Transfer
- Prefer posting from the same device that took the photos, picking originals.
- If you must use a desktop, copy via cable or a full-quality share, then confirm file size did not collapse.
- Name or folder the set by stock number so the wrong 800-pixel folder does not get grabbed. A naming system is a separate discipline; the rule here is "originals live together, derivatives are labeled."
Pre-upload check
| Check | Pass | Fail |
|---|---|---|
| Source | Camera roll original | Chat download, screenshot |
| Sharpness | Badge and miles readable | Soft, smeared, pixelated |
| Size | Typical for a modern phone JPEG | Tiny (failed compress) or huge outlier |
| Content | This unit, this day | Old auction thumbnails |
| Cover | Landscape three-quarter of this unit | Random interior as cover |
If two photos in a set are tiny and the rest are normal, those two were usually forwarded. Replace them.
Failed uploads
When a post fails, do not immediately assume an account restriction. Check file path, network, and whether one image is an enormous outlier. Replace the outlier and retry. If the account actually received a notice, follow that notice. File size is one cause of operational failure among several.
How Many Photos vs How Heavy
A complete set of reasonably sized photos beats a short set of giant ones and a long set of mush.
- Complete coverage still follows The Dealer Photo Checklist for Facebook Marketplace Vehicle Listings.
- Duplicate angles at the same resolution waste upload time and buyer attention. One good three-quarter, not five.
- Close-ups can be slightly tighter files; they still need to be originals.
If posting is timing out on cellular in the lot, move to store Wi-Fi for the upload step, or post from the device that already has the files on Wi-Fi. Do not solve a network problem by shrinking every image until the cluster is unreadable.
How PostToMarket Automates This
Photo resolution and file size for Marketplace uploads become a store problem when each rep has a different path: one posts originals, one posts chat compressions, one dumps a folder of mixed stock numbers. The posting tool cannot invent sharpness, but it can force a moment where a human picks the files that will actually go live, at a human pace, from a queue.
- Facebook photo picker is the selection step. Choose the camera-roll originals. Leave the Messenger downloads unselected.
- One vehicle at a time with human-like delays and server-enforced daily limits so a failed giant file does not fire a burst of retries that looks like bot behavior. PostToMarket is not affiliated with Meta; pacing reduces operational mistakes, it does not guarantee approval or reach.
- Inventory statuses (draft, posting, posted, failed) surface a failed upload so someone can replace a bad file instead of assuming the listing is live.
- Per-rep queues keep each person's photo set attached to their work. Managers assign associate queues for "shoot and post these stock numbers" so files do not bounce through group chat.
- Mobile dashboard lets you reorder the queue toward units whose photos are already on the phone, which is the highest-quality path.
- Mark as sold and archive so old, twice-compressed galleries are not still circulating.
Unlimited inventory means the record can wait in draft until originals are in hand. That is better than posting a 200-kilobyte cover because someone wanted the unit live before lunch.
Stop Posting the Copy of the Copy
Photo resolution and file size for Marketplace uploads are a pipeline standard: camera-app originals, no chat compression, modest edits, a file-size sanity check, and a failed-post review before you blame the account. Sharp, honest photos still get compressed. They survive it. Screenshots do not.
PostToMarket includes a photo picker on every listing, queues so ownership is clear, and AutoPost that submits one vehicle at a time. Starter is $59 per month for a solo seller or independent lot with a single login. Dealership is $299 per month for up to 13 team logins so associates can post from the device that actually took the pictures.
Start your 10-day free trial with secure Stripe checkout. Connect inventory, pick originals instead of forwards, and cancel anytime.