* [raster] Clip the edge sweep's column walk to the surface edge_sweep_row() walked every fixed-point pixel column an edge spans, even though columns right of the surface contribute nothing and columns left of it only contribute a cover delta that telescopes into column 0. A near-horizontal edge with extreme coordinates could span ~2^24 columns per row, making sweep cost proportional to coordinate range instead of surface width: the ClusterFuzz testcase took 114s in a plain release build. Fold the left-of-surface portion of the walk into a single column-0 cover update, skip the right-of-surface portion, and enter/exit the per-column loop at the visible window. Jumping the incremental fy accumulator by k*delta_fy is exact, since the increment is constant and the running sums are bounded, so output is bit-identical; verified by comparing 178 hb-raster renders (draw and paint paths, several fonts, sizes, and negative-margin crops that clip edges off-surface) byte-for-byte against the previous code. The testcase now runs in 0.17s. Also add it as a fuzz seed. Fixes https://oss-fuzz.com/testcase-detail/5267980968329216 Assisted-by: Claude Fable 5 <noreply@anthropic.com> * [raster] Keep an unclipped fast path in the edge sweep The window clipping added in the previous commit made every multi-column edge-row pay for the clip setup, measurable as ~1% more instructions rasterizing all glyphs of NotoSansCJKsc/SourceHanSans-VF at 256px with hb-raster-all. Guard it with a two-compare fully-inside-the-surface check and walk such edges with the original unclipped code, which is also the everyday case: auto-sized surfaces always contain their edges. Interleaved perf-stat A/B (5 rounds, all glyphs at 256px): instruction overhead drops to +0.24% (CJK) / +0.9% (AwamiNastaliq, tiny workload); cycles flat to -1.3%, within noise. Output remains bit-identical on the 178-render comparison matrix, and the oss-fuzz 5267980968329216 testcase stays at 0.19s. Assisted-by: Claude Fable 5 <noreply@anthropic.com> * [raster] Charge column spans in the pixel-work estimate hb_raster_draw_get_pixel_work() charged each edge only its scanline span, so a nearly-horizontal edge crossing one pixel row but sweeping the full surface width cost up to `width` cells while being charged 2 units — the paint path's pixel-budget precharge could undercharge the sweep by a factor of the surface width. This is the same blind spot that let the previous commits' column-walk timeout through the paint path's precharge. Charge each edge its column span too, clipped to the surface width the same way the row span is clipped to its height. Since an edge is a straight segment, row span plus clipped column span is a true upper bound on the post-clipping sweep work. Normal outlines are barely affected: flattening yields short segments whose column spans are commensurate with their row spans, far below the 2^26 budget. No rendering change: the 178-render comparison matrix remains bit-identical and the full test suite passes. Assisted-by: Claude Fable 5 <noreply@anthropic.com>
HarfBuzz
HarfBuzz started as a text shaping engine but has grown into a
full font platform — the ffmpeg of text shaping. It primarily
supports OpenType, but also Apple Advanced Typography.
HarfBuzz shapes the majority of text on modern screens.
HarfBuzz is optimized for robustness, correctness, and performance — in that order. Achieve all.
Try it live at harfbuzz-world.cc — an interactive playground for shaping, subsetting, rasterization, vector output, and GPU rendering, all running in your browser.
Here is a quick map of its components:
Core libraries
| Library | Description |
|---|---|
| libharfbuzz | Text shaping, draw API, paint API. Highly configurable (see CONFIG.md). Optional integration backends compiled in: hb-ft (FreeType), hb-coretext (macOS), hb-uniscribe (Windows), hb-directwrite (Windows), hb-gdi (Windows), hb-glib, hb-graphite2. |
| libharfbuzz-subset | Font subsetting and variable-font instancing. |
Auxiliary libraries
| Library | Description |
|---|---|
| libharfbuzz-icu | ICU Unicode integration. |
| libharfbuzz-cairo | Cairo rendering integration. |
| libharfbuzz-gobject | GObject/GI bindings. |
Experimental libraries
| Library | Description |
|---|---|
| libharfbuzz-raster | Glyph rasterization to bitmaps, including color fonts. Uses hb-draw and hb-paint. |
| libharfbuzz-vector | Glyph output to vector formats (currently SVG), including color fonts. Uses hb-draw and hb-paint. |
| libharfbuzz-gpu | Encodes glyph outlines for GPU rasterization (Slug algorithm). Provides shader sources in GLSL, WGSL, MSL, and HLSL. Live demo. |
Notable missing feature: font hinting (including autohinting) is not implemented. For hinted rasterization, use FreeType or Skrifa.
For simplified builds, amalgamated sources are available:
harfbuzz.cc (just libharfbuzz), harfbuzz-subset.cc (just
libharfbuzz-subset), or harfbuzz-world.cc (everything, driven
by a custom hb-features.h). For a live in-browser playground
plus a worked example of the world.cc single-file build, see
harfbuzz-world.cc.
Command-line tools
| Tool | Description |
|---|---|
| hb-shape | Shape text and display glyph output. |
| hb-view | Render shaped text to an image. |
| hb-subset | Subset and optimize fonts. |
| hb-info | Display font metadata. |
| hb-raster | Render glyphs to bitmap images. |
| hb-vector | Render glyphs to vector formats (SVG). |
| hb-gpu | Interactive GPU text rendering. |
The canonical source tree and bug trackers are available on github. Both development and user support discussion around HarfBuzz happen on github as well.
For license information, see COPYING.
API stability
The API that comes with hb.h will not change incompatibly. Other, peripheral,
headers are more likely to go through minor modifications, but again, we do our
best to never change API in an incompatible way. We will never break the ABI.
The API and ABI are stable even across major version number jumps. In fact, current HarfBuzz is API/ABI compatible all the way back to the 0.9.x series. If one day we need to break the API/ABI, that would be called a new library.
As such, we bump the major version number only when we add major new features, the minor version when there is new API, and the micro version when there are bug fixes.
Documentation
For user manual as well as API documentation, check: https://harfbuzz.github.io
Download
Tarball releases and Win32/Win64 binary bundles are available on the github releases page.
Development
For build information, see BUILD.md.
For custom configurations, see CONFIG.md.
For testing and profiling, see TESTING.md.
For using with Python, see README.python.md. There is also uharfbuzz.
For cross-compiling to Windows from Linux or macOS, see README.mingw.md.
To report bugs or submit patches please use github issues and pull-requests.
Developer documents
To get a better idea of where HarfBuzz stands in the text rendering stack you may want to read State of Text Rendering 2024. Here are a few presentation slides about HarfBuzz over the years:
- 2026 – HarfBuzz at 20!
- 2016 – Ten Years of HarfBuzz
- 2014 – Unicode, OpenType, and HarfBuzz: Closing the Circle
- 2012 – HarfBuzz, The Free and Open Text Shaping Engine
- 2009 – HarfBuzz: the Free and Open Shaping Engine
More presentations and papers are available on behdad's website. In particular, the following studies are relevant to HarfBuzz development:
- 2025 – AAT layout caches
- 2025 – OpenType Layout lookup caches
- 2025 – Introducing HarfRust
- 2025 – Subsetting
- 2025 – Caching
- 2025 –
hb-decycler - 2022 –
hb-iter - 2022 – A C library written in C++
- 2022 – The case of the slow
hb-ft>h_advancefunction - 2022 – PackTab: A static integer table packer
- 2020 – HarfBuzz OT+AAT "Unishaper"
- 2014 – Building the Indic Shaper
- 2012 – Memory Consumption
Name
HarfBuzz /hærfˈbɒːz/
From Persian حرف (Harf: letter) and باز (Buzz: open). Transliteration of the Persian calque for OpenType.
As a noun: The Open Source text shaping engine.
As an adjective: Insincerely talkative; glib. A nod to the GNOME project where HarfBuzz originates from.
The logo shows حرفباز in the IranNastaliq font, on a Damascus steel background.
Background: Originally there was this font format called TrueType. People and companies started calling their type engines all things ending in Type: FreeType, CoolType, ClearType, etc. And then came OpenType, which is the successor of TrueType. So, for my OpenType implementation, I decided to stick with the concept but use the Persian translation. Which is fitting given that Persian is written in the Arabic script, and OpenType is an extension of TrueType that adds support for complex script rendering, and HarfBuzz is an implementation of OpenType text shaping.
Users
HarfBuzz is used in Android, Chrome, ChromeOS, Firefox, Flutter, GNOME, GTK+, KDE, Qt, LibreOffice, OpenJDK, XeTeX, Adobe Photoshop, Illustrator, InDesign, Microsoft Edge, Amazon Kindle, PlayStation, Godot Engine, Unreal Engine, Figma, Canva, QuarkXPress, Scribus, smart TVs, car displays, and many other places.
