Frutiger’s historical design and the Linotype resource
Linotype credits Adrian Frutiger with OCR B in 1968 for optical character recognition requirements associated with the European Computer Manufacturers Association. Its account places human reading alongside machine recognition. The linked publisher resource is OCR B Pro Regular and describes that edition as monospaced.
Keep that history separate from a digital package’s later catalog debut or a local file’s version. The Linotype specimen supplies the original publisher reference for that particular resource.
Microsoft’s OCRB record is an edition-specific source
Microsoft’s Typography page is titled OCRB and discusses OCR-B in its overview. Its metadata lists Ocrb.ttf and records Fixed pitch: False. Linotype’s monospaced description and Microsoft’s fixed-pitch field should remain tied to their own entries; neither is a universal guarantee about every file named OCRB.
The local control on this page requests an installed face named OCRB. If it loads, that establishes local availability rather than a match to Linotype’s files or a verified release version. Read the Microsoft entry alongside the actual installed font information before a production handoff.
Build a letter-and-number proof with the actual wording
Start with 0123456789 O0 I1l, then add the real names, punctuation and identifiers needed by the project. Compare the output at its intended size, including a narrow information block and the longest identifier. Keep an ordinary-text reference beside the proof so a similar-looking replacement cannot conceal an encoding mistake.
Roboto Mono, Source Code Pro and Cousine are independent comparison fonts here, not OCR-B editions. Use the same wording across them to study a different technical reading rhythm. Matching appearance does not establish matching character inventories, metrics or scanner behavior.
Keep visual design separate from operational OCR requirements
For a poster or other graphic, judge the actual letter spacing and hierarchy beside supporting text. For a document that will be scanned, follow that workflow’s required font, size, printing and validation process rather than substituting a visually similar comparison. A family name alone does not prove that the final output satisfies a particular standard.
OCR software interprets an image and produces text. An OCR-B font renders characters that are already text; selecting it does not convert a photograph or scan into an editable document.
Retain the exact source, files and preview limitations
Use the separately labeled Linotype and Microsoft links to investigate the corresponding editions and acquisition routes. This site does not supply their font software or grant a redistribution license. The local preview checks the named default face on your device; it does not expose every style or prove coverage for every character.
Keep the selected publisher, full font name and supplied terms with the editable source document. Ordinary copied text does not carry the font into another application. For a handoff, distinguish an installed file, a rendered image and font file formats explicitly.
Your questions, answered.
Who designed OCR B?
Linotype credits Adrian Frutiger and dates the design to 1968, connecting it to European optical character recognition requirements.
Does OCR B convert an image into editable text?
No. It is a typeface associated with optical character recognition workflows. Converting an image to text requires OCR software.
Are the editable alternatives approved substitutes for a scanning standard?
No. They are independent visual comparisons. Use the font and output requirements specified by the actual scanning workflow.
Does an installed OCRB preview prove it is the Linotype edition?
No. It confirms that the browser can load a local face with that name. Check the actual file and edition information separately.
Does this page distribute OCR-B or OCRB font files?
No. It provides source links, an optional installed-font preview and independently named comparison fonts.
Sources & background
Sources supporting this page’s explanations. Practical examples are our editorial suggestions.