---
title: "Turbo Pascal 3.02 fit a compiler and editor into 39,731 bytes, smaller than one photo on Apple’s 2011 site"
url: https://badiyaa.com/turbo-pascal-39731-bytes-compiler/
published: 2026-11-16T10:54:00+00:00
modified: 2026-11-16T10:54:00+00:00
section: Tech
publisher: Badiyaa
---

# Turbo Pascal 3.02 fit a compiler and editor into 39,731 bytes, smaller than one photo on Apple’s 2011 site

Turbo Pascal 3.02, Borland's 1986 compiler and editor, took up just 39,731 bytes, less than half the size of the minified jQuery 1.6 library.

The whole of Turbo Pascal 3.02, a complete programming language compiler with its own built-in editor, took up 39,731 bytes. That is smaller than many single photos on a modern website, and the comparison has been doing the rounds again among programmers this week.

The figure comes from “Things That Turbo Pascal Is Smaller Than,” a short 2011 post by James Hague, a game designer and programmer who writes the blog Programming in the Twenty-First Century. He lined up the 1986-era tool against everyday files of the time and found it lost almost every size contest.

## What it was smaller than in 2011

- The minified jQuery 1.6 JavaScript library: 90,518 bytes.

- The home page of a major web portal: 219,583 bytes.

- The photo of the white iPhone 4S on Apple’s website: 190,157 bytes.

- The humble “touch” command in Mac OS X Lion: 44,016 bytes.

- The online encyclopedia article on the C++ language: 214,251 bytes.

Run the numbers and the gap is wide. The jQuery file was about 2.3 times the size of the entire Turbo Pascal program, and that web portal home page about 5.5 times. Even a single Unix utility whose only job is to update a file’s timestamp outweighed it by about 4,300 bytes.

There was a reason for that thrift. Early PC programs in this format had to squeeze code into 64 kilobytes, or 65,536 bytes, so Turbo Pascal 3.02 filled only about 61% of that space while carrying a compiler, an editor and the run-time support programs needed.

## How Borland made it so small and fast

Turbo Pascal first shipped on November 20, 1983, which makes this Friday its 43rd anniversary. Danish programmer Anders Hejlsberg wrote the compiler core, and Borland, the young company run by Philippe Kahn, wrapped an editor around it and sold the bundle by mail order for $49.95, at a time when rival professional tools could cost hundreds of dollars.

Most programmers back then worked in three separate steps: edit, compile, then link, often swapping floppy disks between each. Turbo Pascal kept everything in memory and compiled in a single pass, using code written in assembly language. You could write a program and run it moments later without leaving the editor.

It sold far beyond expectations, about 250,000 copies in two years. Borland also skipped copy protection, shipping it under a “Book License” that told buyers to “treat this software just like a book.”

The tool had one famous time bomb. A unit called CRT, included in several later versions, measured processor speed when a program started, and on chips faster than roughly 200 MHz its counter overflowed, crashing programs with “Runtime Error 200.” Patches followed as processors kept getting faster.

## Where it went next

Hejlsberg went on to architect the first three versions of Borland Delphi, which replaced Turbo Pascal by 1995. Borland later released several old versions as free downloads because of their historical interest, including version 3.02 in February 2000.

Badiyaa has looked at other moments when software size and detail mattered enormously, from the [Knight Capital code update that lost $460 million in 45 minutes](https://badiyaa.com/knight-capital-460-million-software-glitch/) to the [Utah teapot that every graphics student still renders](https://badiyaa.com/utah-teapot-3d-model-history/).

## Further reading

- [Wikipedia: Turbo Pascal](https://en.wikipedia.org/wiki/Turbo_Pascal)

*Image: Michael Holley (Swtpc6800), Public domain via Wikimedia Commons*

*This article was produced with AI assistance and reviewed by our Editorial Desk. [How we work](https://badiyaa.com/editorial-policy/).*
