- ✓Boston Dynamics' Atlas robots use stereo depth cameras capturing hundreds of frames per second — that data is compressed as H.264 video for real-time transmission, not as JPEG still images
- ✓Neural networks trained on image data don't 'see' JPEG artifacts the way humans do — they can misinterpret compression artifacts as real visual features, which degrades model performance
- ✓Training datasets for AI vision models (ImageNet, LAION) are stored in high-quality or lossless formats specifically to prevent compression artifacts from becoming false 'features' the model learns
- ✓When you submit a photo to an AI tool like GPT-4o's vision API or Gemini Vision, a heavily JPEG-compressed image loses edge detail and texture that the model uses for identification — quality matters for AI too
- ✓The robot and the consumer tool both need the same thing from their images: preserved spatial gradients and edge information — which is exactly what quality-preserving compression protects

Google DeepMind and Boston Dynamics announced a partnership this week to integrate DeepMind's Gemini Robotics foundation models with Boston Dynamics' next-generation Atlas humanoid robots. The premise: Atlas gets a brain upgrade, using DeepMind's AI to handle more complex, real-world tasks that require understanding context rather than just following pre-programmed movements.
The robotics story is interesting on its own. What's more useful for thinking about how images work — and why compression matters — is what it reveals about how AI systems actually see and process visual data, which is fundamentally different from how human image formats are built.
What a Robot's Camera Actually Captures
Atlas has stereo cameras — two calibrated cameras at a fixed distance from each other, capturing simultaneous frames that can be used to compute depth. The robot uses those depth maps to understand the three-dimensional structure of its environment in real time: where is the floor, how far away is the obstacle, what is the shape of the object it's about to pick up.
The cameras capture at roughly 60 to 100 frames per second for navigation, with some additional sensors running faster for collision detection. At even 60fps at 1920×1080 resolution, that's 60 images per second per camera — 120 raw images per second from just the main stereo pair. This cannot be stored or transmitted as individual JPEG files. The data rate would be unmanageable and the inter-frame redundancy (most of the scene doesn't change frame-to-frame) would be thrown away.
Instead, robot vision systems use video codecs — typically H.264 or H.265. Video codecs are fundamentally different from still image codecs: they encode temporal differences between frames (if a pixel hasn't changed, why encode it again?), which achieves far higher compression ratios for moving camera feeds than any per-frame codec can. For depth data specifically, robots use floating-point formats that preserve the continuous range of distance values rather than mapping to the 0–255 integer range of consumer image formats.
Why Neural Networks Don't See Compression the Way Humans Do
Here's the part that matters for how you submit images to AI tools. When a human looks at a JPEG that's compressed too hard, they see blurriness, block edges, colored fringing. These are recognizable as compression artifacts — things that "look wrong" — and a human viewer knows to discount them.
Neural networks don't have this abstraction. A convolutional neural network's early layers respond to edges, gradients, and texture patterns. A JPEG block boundary — the hard edge between two 8×8 compression blocks — looks like a real edge to the network's feature detectors. Ringing artifacts around text or logos look like real texture variations. The network's early layers extract features from these artifacts just as readily as from real image content, which propagates errors through the model.
This is well-documented in the adversarial examples literature: extremely subtle pixel-level changes can dramatically change a neural network's output while looking completely unchanged to a human. Compression artifacts are a less extreme version of the same phenomenon — they introduce systematic pixel-level corruption that the model wasn't trained to ignore.
What This Means When You Use AI Image Tools
When you submit a photo to GPT-4o vision, Gemini Vision, or any AI image tool, the model is processing your image through a pipeline that extracts feature representations. The quality of those features depends on the quality of the input image.
Practical examples where compression quality matters:
Document OCR: A scan of a document compressed at JPEG Q60 will have lower text recognition accuracy than the same scan at Q92, particularly for small fonts, handwriting, or documents with complex backgrounds. The block artifacts around letter edges confuse character boundary detection.
Product identification: An AI tool identifying a product from a photo will have lower confidence for brand logos, fine texture (fabric material, surface finish), and small text on packaging when the source image is heavily compressed.
Medical imaging: This is where the stakes are highest. Radiological images are stored in DICOM format at lossless quality for this exact reason — JPEG compression of an X-ray or MRI scan can make real pathological features ambiguous or create artifact patterns that resemble findings.
Face recognition: Recognition accuracy for face verification systems degrades measurably below JPEG Q80 for typical portrait photos. Compression smears the fine detail around eye features that face recognition models rely on for matching.
Training Data Is Stored Losslessly for a Reason
The AI models that are now powering Gemini Robotics in Atlas robots were trained on massive image datasets. ImageNet — one of the foundational training sets for image classification — is distributed as individual JPEG files, but at high quality settings (typically Q95+). LAION-5B, a more recent large-scale dataset, stores images at their source quality rather than re-compressing them.
This is deliberate. If a neural network trains on millions of JPEG-compressed images, it learns to recognize compression artifacts as normal. It builds a feature extractor calibrated to operate on slightly degraded input. That works fine if all your inference images are at the same compression level, but it degrades performance when you need the model to identify fine-grained features.
The robots being trained at Boston Dynamics and DeepMind are processing sensor data that never passes through consumer compression codecs. Their training data is sensor captures or high-fidelity simulations. The result is models that are very good at interpreting clean, high-quality visual input — and potentially more sensitive to degradation from consumer-grade compression than a model trained on JPEG data would be.
The Common Thread
A Boston Dynamics robot and a ChatGPT image prompt look nothing alike as systems. One is a 90kg physical machine running real-time sensor fusion. The other is a web API call. But they have the same requirement from their image input: spatial gradients and edges need to be accurate, because that's the raw material that neural networks build their understanding from.
JPEG compression, when it degrades those gradients and introduces false edges, makes life harder for both systems. The robot gets noisier depth estimates. The vision API gets lower confidence classifications. The human looking at the JPEG might not see the problem. The neural network processes the artifacts anyway.
The implication for practical use: if you're using AI image tools for anything where accuracy matters — extracting text from documents, identifying products, analyzing photos — submit the highest-quality version you have. Convert your messenger-compressed photos back to quality before feeding them to the model. The model is almost certainly better than the quality of image you're giving it.
Related reading:
- Compress AI-Generated Images from Midjourney and DALL-E — the other direction: AI outputs and how to compress them without destroying the synthetic detail
- EU AI Act — What It Means for Images on Your Website in 2026 — regulation framing for AI and image content together
- The Future of AV1 and Beyond — where next-generation compression codecs are headed and how they interact with AI pipelines
Frequently asked questions
What image format do robots like Atlas actually use to process visual data?
Not JPEG. Industrial robot cameras output raw sensor data that gets processed in real-time by the onboard computer. For transmission and logging, the video stream is typically compressed using H.264 or H.265 video codecs — which are temporally aware (they use previous frames to compress the current one) rather than compressing each frame independently like JPEG. For depth data specifically, robots use specialized formats like ROS depth image messages or floating-point depth maps that preserve the continuous range information needed for spatial reasoning.
Does image compression quality affect how well AI tools analyze a photo?
Yes, measurably. AI vision models — including the ones powering ChatGPT vision, Gemini Vision, and Claude's image understanding — process photos by extracting feature representations from them. JPEG artifacts (block edges, ringing, chroma smearing) look like real edges and texture variations to a neural network's early convolutional layers. A heavily compressed photo of a document will have lower OCR accuracy than a high-quality version of the same document. A compressed product photo submitted to an AI classifier will have lower confidence scores for fine details like brand logos or material texture.
Continue reading
Try Optimage — it's free
Compress, convert, and optimize images in seconds. No sign-up, no limits.
Start Optimizing Free