Embedded OpenType traces back to Internet Explorer 4 in 1997, when Microsoft first built font-linking into a browser \u2014 years before WOFF or WOFF2 existed. The underlying problem was already familiar: type foundries would not license fonts for the open web if those fonts could simply be lifted from a linked file and reused without payment. Microsoft’s answer was to wrap the font in a proprietary container with subsetting, LZ-based compression (related to Agfa’s MicroType Express), and a “rooting” mechanism \u2014 an encrypted list of domains authorized to display the embedded font, checked by IE’s own decryption library. Microsoft submitted EOT to the W3C, first bundled into a 2007 CSS3 submission and then as a standalone specification on March 18, 2008, seeking broader adoption.<\/p>\n
The W3C ultimately did not adopt EOT as a recommendation, favoring the openly developed WOFF format instead, and no browser other than Internet Explorer ever implemented EOT rendering. That left EOT as a single-vendor, single-browser format for its entire working life, useful only as one entry in a multi-format @font-face fallback stack (alongside WOFF, TTF and SVG) during the transitional years when IE6-IE11 still commanded meaningful market share.<\/p>\n
For DAM purposes, EOT is almost entirely a historical concern rather than an active production format. A DAM that inherits an older website’s asset library may still hold .eot files generated for legacy IE support; these should be cataloged as deprecated renditions rather than refreshed or regenerated, since maintaining IE-only font delivery no longer serves any practical audience for the vast majority of sites. The one place EOT still matters to a DAM is licensing history: because EOT’s rooting mechanism ties a font file to specific domains, any archived EOT asset can be a useful record of which domains a foundry historically authorized for web embedding, even after the format itself is retired from active use.<\/p>\n
EOT’s DRM-oriented design \u2014 encryption plus a trusted-domain list \u2014 also foreshadowed the licensing conversations that persist around every web font format today: WOFF and WOFF2 dropped the built-in encryption but the underlying obligation, that a font file may only be embedded on domains the foundry has licensed, did not go away. A DAM tracking font assets should carry that licensing scope as explicit metadata regardless of which container format wraps the font.<\/p>","protected":false},"excerpt":{"rendered":"
EOT is a proprietary Microsoft container format that compresses and DRM-wraps TrueType or OpenType fonts for embedding in web pages, supported only by Internet Explorer.<\/p>\n","protected":false},"author":0,"featured_media":0,"template":"","meta":{"footnotes":"","faq":[{"question":"Is EOT still relevant for new web projects in a DAM's asset pipeline?","answer":"No \u2014 EOT should not be generated for new builds. It exists solely for Internet Explorer 4 through 11, and Microsoft's own successor browser, Edge, dropped EOT support entirely. The W3C standardized WOFF and WOFF2 instead, and virtually every current browser renders WOFF2 natively. A DAM's web-font pipeline should output WOFF2 as the primary format, with WOFF as a fallback, and skip the EOT step, since it only adds build complexity for a rendering target with no remaining production traffic."},{"question":"Why does EOT include encryption and a domain list?","answer":"Microsoft designed EOT with a 'rooting' mechanism \u2014 an encrypted list of authorized domains checked by Internet Explorer's decryption library \u2014 to reassure type foundries that embedded fonts couldn't be freely reused off the licensed site."},{"question":"Which browsers support EOT?","answer":"Only Internet Explorer supported EOT natively, from version 4 in 1997 through Internet Explorer 11. No other browser \u2014 not Chrome, Firefox, Safari, Opera, nor Microsoft's own Edge, which replaced IE \u2014 ever implemented EOT rendering; each adopted WOFF or WOFF2 instead. For a DAM, this means an EOT file inherited from an old asset library cannot be served directly to today's visitors \u2014 it must first be converted to WOFF\/WOFF2 or the original TrueType\/OpenType source before it will render in any current browser."},{"question":"Did the W3C ever standardize EOT?","answer":"No. Microsoft submitted the EOT specification to the W3C twice \u2014 first folded into a 2007 CSS3 submission, then as a standalone submission on March 18, 2008, alongside Monotype Imaging's MicroType Express compression spec. The W3C never advanced it past 'submission' status \u2014 the category for member-proposed specs it has not endorsed \u2014 and instead developed WOFF, later WOFF2, as its Recommendation. For a DAM, this matters: WOFF\/WOFF2 are the standardized formats, while EOT remains a proprietary, single-vendor format that never left submission."},{"question":"Can an archived EOT file be converted to a modern format?","answer":"Often yes, using tools like FontForge or dedicated EOT-to-TTF converters, though the result should still be checked against the original font's license terms before reuse, since EOT's subsetting may mean it lacks the full original character set."},{"question":"Should a DAM delete old EOT files from an inherited asset library?","answer":"Deletion is unnecessary and can be counterproductive. EOT files are typically small, so storage cost is negligible, while the file itself documents which domains were originally authorized under the format's encrypted 'rooting' mechanism \u2014 useful licensing history if the underlying font's usage rights are ever questioned. The safer approach is to tag each EOT file as deprecated\/legacy in the DAM's metadata, exclude it from active build and delivery pipelines so it's never served to a live site, but retain it alongside its original TrueType\/OpenType source (if archived) as a record of the asset's licensing and deployment history."},{"question":"What compression does EOT use compared to WOFF?","answer":"EOT typically compresses fonts using MicroType Express, an LZ-based compression method contributed by Agfa\/Monotype, combined with character subsetting that strips out glyphs not used on the source page \u2014 together these keep file sizes down while also enabling EOT's encrypted domain-authorization ('rooting') layer, which WOFF and WOFF2 don't have. WOFF wraps the original TrueType\/OpenType tables using zlib\/deflate compression plus metadata and private-data blocks, while WOFF2 improves on this with Brotli compression and additional table-transform tricks, generally yielding smaller files than either EOT or WOFF for the same source font, with no DRM overhead."},{"question":"Does EOT support the full OpenType\/TrueType character set?","answer":"Typically no. EOT files are usually subsetted \u2014 trimmed down to include only the characters actually referenced on the specific source page, which is part of how the format kept downloads small on 1990s-era connections. That means an archived EOT file may be missing glyphs for languages, symbols, or punctuation the original page never used. For a DAM, this makes EOT unsuitable as a canonical master: if a font needs to be reused on a different page, in another language, or with expanded character coverage, the pipeline should return to the original full TrueType\/OpenType source file rather than the subsetted EOT."}],"checked_date":"2026-08-11","sources":[{"statement":"Font embedding was introduced with Internet Explorer 4 (released September 22, 1997); EOT supported in IE4 through IE11, no other browser.","source_name":"Wikipedia \/ web search cross-check","url":"https:\/\/en.wikipedia.org\/wiki\/Internet_Explorer_4","checked":"2026-08-07"},{"statement":"EOT was designed by Microsoft with subsetting, LZ compression (related to Agfa MicroType Express), and encrypted 'trusted roots' domain restriction.","source_name":"Wikipedia: Embedded OpenType","url":"https:\/\/en.wikipedia.org\/wiki\/Embedded_OpenType","checked":"2026-08-07"},{"statement":"Microsoft submitted EOT to the W3C in 2007 as part of a CSS3 submission (rejected), then resubmitted as a standalone submission March 18, 2008; W3C Submission page confirms EOT submission.","source_name":"W3C Member Submission: Embedded OpenType (EOT) File Format","url":"https:\/\/www.w3.org\/submissions\/EOT\/","checked":"2026-08-07"}],"kicker":"","fact_checker":0,"reading_time":0,"revisions":[],"seo_title":"EOT font format: what it is, IE support and modern successors","seo_description":"","noindex":false,"ext":"eot","full_name":"Embedded OpenType","vendor_name":"Microsoft","introduced":"Font embedding introduced with Internet Explorer 4 (1997); EOT format submitted to W3C as a standalone submission on March 18, 2008 (after an earlier 2007 CSS3 submission)","container_notes":"An EOT file wraps a subsetted TrueType\/OpenType font (typically reduced to only the characters used on the page), compressed with LZ compression related to Agfa's MicroType Express, and adds a header carrying font metadata plus DRM-style protections: an encrypted \"root string\" list of domains authorized to use the embedded font, checked by a proprietary decryption library in Internet Explorer. This rooting\/encryption mechanism, meant to reassure foundries against unauthorized reuse, is unique to EOT among the major web font containers.","open_with":[{"platform":"Legacy Internet Explorer (4 through 11)","how":"The only browser family that natively renders EOT-embedded fonts via @font-face; no other browser ever implemented support"},{"platform":"FontForge","how":"Can open\/inspect some EOT files and convert them to TTF\/OTF for reuse, subject to the font's original DRM\/subsetting"},{"platform":"eot2ttf \/ online converters","how":"Command-line and web-based EOT-to-TTF converters (e.g. Transfonter, CloudConvert) unpack the wrapped sfnt data for migration to modern formats"},{"platform":"Microsoft's WEFT (Web Embedding Fonts Tool)","how":"Microsoft's original legacy authoring tool for generating and rooting EOT files (Windows-only, largely obsolete)"}],"archive_advice":"EOT should be treated as a legacy format in any DAM: do not generate new EOT renditions for current projects, since it is unsupported outside old Internet Explorer and was rejected by the W3C in favor of WOFF. If legacy EOT files exist in an archive (e.g. from pre-2015 site builds), retain them only for historical\/compliance reference or IE11-support edge cases, tag them clearly as deprecated, and rely on the source desktop font plus WOFF\/WOFF2 renditions for all active and future web delivery.","related":[],"tool_link":""},"silo":[23],"class_list":["post-2993","format","type-format","status-publish","hentry","silo-formats"],"_links":{"self":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/2993","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format"}],"about":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/types\/format"}],"version-history":[{"count":1,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/2993\/revisions"}],"predecessor-version":[{"id":3278,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/format\/2993\/revisions\/3278"}],"wp:attachment":[{"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/media?parent=2993"}],"wp:term":[{"taxonomy":"silo","embeddable":true,"href":"https:\/\/picajet.com\/articles\/wp-json\/wp\/v2\/silo?post=2993"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}