Computers interpret information only when they know how its data is represented. A bit pattern has no built-in meaning: a convention, encoding, or format tells a device whether those bits stand for text, a number, an image, sound, or part of a structured record.
Information and its representation are different
Information is knowledge that can be expressed in different forms. Representation is the mapping and organization used to store, process, communicate, or interpret that knowledge. The same underlying information can therefore be represented in more than one way, and the same sequence of bits can be interpreted differently under different conventions.
As an Amazon Associate I earn from qualifying purchases.
For example, a group of bits might be interpreted as a number, a character, a color value, or an instruction. The bits do not identify which interpretation is correct by themselves. A sender and receiver—or a program and the data it reads—must share the relevant rules. NIST’s glossary likewise notes that the meaning of data depends on the conventions used to represent it: NIST: Information.
How conventions make bits interpretable
A representation scheme maps values to meanings and specifies how those values are organized. The convention may define which codes correspond to characters, where fields begin and end in a record, or how a sequence of samples or pixels should be decoded. Software and hardware apply those rules to transform stored values into something they can use or display.
#1 Best Overall
Digital systems use defined encoding schemes to map bits to numbers, characters, images, audio, and structured data. If two systems use different conventions—or disagree about which convention applies—they may produce different results from the same bytes. This is why a file often needs a known format, and why communication protocols specify how data is arranged and interpreted. See the IEEE overview of information representation.
Text: code points and encodings
Text makes the distinction between information and representation concrete. Unicode assigns characters numeric code points, while an encoding form specifies how those code point values are represented as code units in a computer. A code point identifies a character in the standard; it is not itself the byte sequence used to store or transmit that character.
The Unicode Standard defines UTF-8, UTF-16, and UTF-32 encoding forms, with 8-, 16-, and 32-bit code units respectively. UTF-8 is byte-oriented and variable-length; its ASCII range uses the same byte values as ASCII, which helps it work with ASCII-based systems. These are different ways to encode Unicode text, not different sets of characters. The Unicode Consortium’s Unicode 18.0.0 introduction and technical introduction to UTF-8 explain the distinction. The Consortium describes Unicode as “the universal character encoding standard for written characters and text.”
Free tools Windows power users keep installed
One-click scans. No signup required.
Images, sound, video, and other media
Representation is not limited to text. An image can be represented through pixel values and color conventions; digital audio can be represented through encoded samples; video combines images over time, often alongside audio and other data. A format defines how such components are coded and organized so compatible software can interpret them.
Multimedia systems may combine text, fonts, service information, audio, video, and graphics. ISO/IEC 16500-6:1999 covers information types and coding and exchange of these components in audiovisual systems. ISO’s catalog identifies this edition as published in December 1999 and last reviewed and confirmed in 2021: ISO/IEC 16500-6:1999.
Representation choices involve tradeoffs
No representation is best for every purpose. When choosing or evaluating an encoding or format, consider how reliably different systems can decode it, how much precision or fidelity it retains, how much storage or transmission capacity it uses, and how easily people or software can interpret the result.
- Interoperability: Systems need compatible conventions and suitable decoders to exchange data successfully.
- Precision and fidelity: A representation may preserve detail, or simplify it according to the format’s rules.
- Compactness: Smaller representations can save storage and transmission capacity, but may involve tradeoffs in retained information.
- Interpretability: A format should make its structure and intended meaning accessible to the people or software that need it.
Compression illustrates the fidelity-versus-size tradeoff. Lossless compression preserves the original content so it can be recovered exactly; lossy compression reduces size by discarding information, so the original cannot be reconstructed exactly from the compressed result. The right choice depends on the content and its purpose, not on a universal ranking of formats. The IEEE overview describes these compression approaches.
Why shared representation matters
A representation works when the systems or people using it agree on its rules. Shared conventions let different software read the same text, exchange records, or decode media consistently. When those conventions are unknown, unsupported, or mismatched, data may appear garbled, be misread, or fail to open as intended.
Best Value
Historical work on external data representation also illustrates that systems need agreement not just on a value’s encoding, but on its type and interpretation. RFC 971, published in January 1986, is an informational survey of those issues rather than a current protocol standard: RFC 971.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
