800x600 originates from SVGA, a display standard introduced in 1989 as an extension of IBM's earlier VGA specification. For most of the 1990s and into the early 2000s, 800x600 was the most common screen resolution in actual use, the default that a huge share of desktop monitors shipped with or were set to. Web design conventions from that era were built around it directly. Designers worked to a roughly 760-pixel content width to account for browser chrome and scrollbars, and images were sized to fit comfortably within that constraint. The 800x600 figure that still shows up as a preset option today is a direct descendant of that period, even though almost no one is browsing the web on an 800x600 display anymore.
What kept the number relevant long after monitors moved past it is that 800x600 turned out to be a genuinely useful size for purposes that have nothing to do with matching a screen resolution. At 4:3, it produces images that are large enough to show real detail but small enough to keep file sizes modest, typically 80 to 200KB for a JPEG photograph at reasonable quality. That balance made it a practical default for inline content images in blog posts, forum attachments, and email bodies, where there was never a need for an image any larger than what a reader would actually view it at.
Why 4:3 specifically, and how it differs from modern widescreen defaults
The 4:3 aspect ratio predates digital displays entirely. It traces back to early film and television formats, where 4:3 was the standard frame shape for decades before 16:9 widescreen became the broadcast and computing default in the 2000s. This history means 4:3 images sit somewhat awkwardly alongside the 16:9 video content and widescreen photography that dominate the modern web. A landscape photo shot on a phone today is typically closer to 4:3 in its native form (depending on the device), which makes the 800x600 frame a reasonably natural fit for ordinary photography without requiring aggressive cropping, unlike forcing the same photo into a 16:9 frame.
Where 800x600 still earns its place today is in contexts where a small, fast-loading, moderately detailed image is exactly what's needed and nothing more. Email body images benefit from staying small since many email clients render images at modest sizes and slow connections matter more for email than for a modern website. Legacy CMS platforms and forum software built years ago often still expect this dimension as a default upload size. And for any inline content image inside an article or blog post where the image supports the text rather than serving as a hero visual, 800x600 is large enough to read clearly without bloating the page. If you need the file size brought down further after resizing, the compress under 200KB tool works well alongside this size for email and CMS uploads with their own size restrictions.