# DataGlyph

> Source: https://docs.barcoder.ai/docs/standards/dataglyph
> research date 2026-06-04 · extracted at 2026-10-03
> Publisher: Barcoder — encyclopedia of QR, barcode and payment-code standards

Specifications:
- [DataGlyph — Wikipedia](https://en.wikipedia.org/wiki/DataGlyph)
- [DataGlyph — Rob Tow (inventor's account)](https://www.tauzero.com/Rob_Tow/DataGlyph.html)

## Overview

**DataGlyph** is a 2D data-encoding scheme developed at **Xerox PARC** that represents bits as tiny **45-degree diagonal strokes** — a stroke leaning one way is a 0, leaning the other way is a 1 <sup>[1][1], [2][2]</sup>. Printed densely, the strokes blend into what looks like a uniform grey **halftone** tint, so a DataGlyph can hide in the background of a document, masquerade as a shaded image, or form a decorative border while invisibly carrying machine-readable data <sup>[1][1]</sup>. The binary payload is protected with **Reed–Solomon error correction**, giving DataGlyphs robustness against print damage and partial occlusion <sup>[1][1]</sup>.

## History

The core idea was conceived by **Rob Tow in 1988** at Xerox PARC's Electronic Document Lab <sup>[2][2]</sup>. Tow's insight was to repurpose the halftone dots used in digital printing as data carriers: "you could make the little dot lean *left* to represent a zero, and to the *right* to represent a one" <sup>[2][2]</sup>. He chose the name "Glyph" for its typographic associations, and Xerox marketing later branded the result **DataGlyph** <sup>[2][2]</sup>.

The technology was patented through the 1990s <sup>[2][2]</sup>:

- **U.S. 5,091,966** (Feb 1992) — Bloomberg & Tow — adaptive scaling for glyph decoding <sup>[2][2]</sup>.
- **U.S. 5,315,098** (May 1994) — Tow — embedding digital data in halftone images <sup>[2][2]</sup>.
- **U.S. 6,076,738** (Jun 2000) — Bloomberg, Hecht, Flores & Tow — self-clocking glyph shape codes <sup>[2][2]</sup>.

DataGlyph became a licensed Xerox product and was incorporated into Xerox's **PaperWorks** system, which encoded document metadata directly onto printed pages <sup>[2][2]</sup>. (David L. Hecht at PARC is associated with the later self-clocking glyph-code work.)

## Technical specification

DataGlyph encodes bits in the orientation of small diagonal marks <sup>[1][1], [2][2]</sup>:

- **Dibit marks** — each glyph is a short line at **45°**; a **downward slope = 0**, an **upward slope = 1** <sup>[1][1]</sup>.
- **Halftone camouflage** — printed densely, the field of glyphs reads as a continuous grey area, "akin to halftone," so it can be tuned to resemble an image, sit behind text, or act as a page border <sup>[1][1]</sup>.
- **Reed–Solomon error correction** — the bit stream is encoded with Reed–Solomon, giving substantial redundancy (a reported redundancy on the order of ~30 %) so the code survives smudging, folds, and partial damage <sup>[1][1]</sup>.
- **Self-clocking glyph codes** — later variants use a self-clocking structure so the reader can recover the grid lattice and synchronise without a separate timing track <sup>[2][2]</sup>.
- **Density** — high for a printed code: figures of around **155 bytes per cm²** at 600 dpi are cited, and digital cards using DataGlyphs reportedly stored on the order of **3 kilobytes** — far above a magnetic stripe <sup>[1][1]</sup>.

## Use cases

- **Embedded document metadata** — Xerox PaperWorks used DataGlyphs to carry routing, indexing, and form metadata invisibly on the printed page <sup>[2][2]</sup>.
- **Secure / value documents** — the halftone camouflage plus Reed–Solomon robustness suited ID cards, tickets, and certificates where data should be present but not obtrusive <sup>[1][1]</sup>.
- **Self-describing forms** — a glyph block printed on a form lets a scanner recover machine-readable instructions about that form <sup>[1][1], [2][2]</sup>.
- **Decorative / steganographic data carrying** — glyphs tuned to look like shading or borders embed data without a visible barcode <sup>[1][1]</sup>.

## Implementations

DataGlyph is **proprietary to Xerox**; there is no open standard or widely available open-source implementation <sup>[1][1], [2][2]</sup>:

- **Xerox DataGlyph toolkit / PaperWorks** — the original licensed encoding/decoding software <sup>[2][2]</sup>.
- **Research decoders** — academic work exists on reading DataGlyphs from camera images (e.g. grayscale-reader research), but these are studies rather than productised libraries <sup>[1][1]</sup>.

State honestly: DataGlyph never developed the broad open-source tooling ecosystem that QR or Data Matrix enjoy; it remained largely a Xerox-controlled technology.

## Comparison

**vs. [QR Code](https://docs.barcoder.ai/docs/standards/qr-code) / [Data Matrix](https://docs.barcoder.ai/docs/standards/data-matrix)** — QR and Data Matrix are overt, standardised (ISO), royalty-free, and ubiquitously supported by free libraries. DataGlyph is covert (it hides as halftone shading), proprietary, and lacks open tooling. Where QR/DM advertise their presence with finder patterns, DataGlyph's design goal is the opposite — to be visually unobtrusive while still carrying meaningful data.

**vs. digital watermarking (e.g. [Digimarc Barcode](https://docs.barcoder.ai/docs/standards/digimarc-barcode))** — both aim for unobtrusive on-page data. A digital watermark is truly imperceptible (modulating existing imagery), whereas a DataGlyph is a visible-but-camouflaged texture of strokes; DataGlyph carries comparatively high capacity and structured error correction at the cost of being a discrete glyph field rather than an invisible signal spread through artwork.

**vs. 1D barcodes** — DataGlyph offers far higher density and Reed–Solomon robustness, plus the ability to blend into a document, but at the price of specialised, non-open readers.

## Fun facts

The whole scheme grew from one elegant observation by Rob Tow in 1988: the halftone dots already sprayed across every printed image could simply be made to **lean left or right** to carry bits, turning ordinary printed shading into a hidden data layer <sup>[2][2]</sup>.

DataGlyphs can be **tuned to look like part of an image, the background behind text, or a decorative border** — so a page can carry kilobytes of machine-readable data without anything that looks like a barcode appearing on it at all <sup>[1][1]</sup>.

## Status

**Legacy.** DataGlyph was an influential Xerox PARC technology of the 1990s that shipped commercially (PaperWorks) but never achieved the open-standard, mass-library adoption of QR Code or Data Matrix <sup>[1][1], [2][2]</sup>. It is best regarded as a historically important, largely superseded proprietary scheme: its ideas (camouflaged high-density on-page data, self-clocking glyph lattices) live on conceptually, but it is not an actively growing standard today.

## Sources

[1]: https://en.wikipedia.org/wiki/DataGlyph
[2]: https://www.tauzero.com/Rob_Tow/DataGlyph.html
[3]: https://scispace.com/pdf/a-grayscale-reader-for-camera-images-of-xerox-dataglyphs-4e1ums043d.pdf
[4]: https://patents.google.com/patent/US6641053B1/en

1. [DataGlyph — Wikipedia][1]
2. [DataGlyph — Rob Tow (inventor's account), Tau Zero][2]
3. [A Grayscale Reader for Camera Images of Xerox DataGlyphs — Moravec][3]
4. [US6641053B1 — Foreground/background document processing with dataglyphs — Google Patents][4]

## Deployments

_No country reports mention this standard by name._

## Regions / aggregations not mapped to a single country

- Universal