# LXGW Neo XiHei: a mainland-standard sans built on IPAex Gothic

> LXGW Neo XiHei rebuilds the Japanese IPAex Gothic glyphs into Simplified Chinese mainland forms, adds Greek, Cyrillic and Vietnamese coverage, and ships a Plus variant that reaches GB 18030-2022 implementation level 2. It is in a stable maintenance phase, so adopt it with that cadence in mind.

**lxgw/LxgwNeoXiHei** — A Chinese sans-serif font derived from IPAex Gothic. 一款衍生于「IPAexゴシック」的中文黑体字型。

- Repository: https://github.com/lxgw/LxgwNeoXiHei
- Stars: 2,664 · Forks: 35
- Language: Unknown
- License: NOASSERTION
- Published: 2026-09-28 · Updated: 2026-09-28 · Language: en
- Canonical page: https://hysenlabs.com/projects/lxgw-lxgwneoxihei

## The problem: Japanese sans glyphs used for mainland Chinese text

IPAex Gothic is a Japanese typeface. Its glyphs follow Japanese conventions, and the README frames LXGW Neo XiHei as an attempt to convert a Japanese-style font into mainland Chinese standard forms. That is a different job from drawing a typeface from scratch. The project starts from the existing outlines of IPAex Gothic and LXGW XiHei (the legacy branch) and reshapes them toward mainland conventions. The README gives concrete examples: the feet on components such as 口, 日, 缶 and 山 in characters like 枸, 间, 陶 and 岩 have been simplified, which the README describes as making the forms more minimal. The target reader is someone setting Simplified Chinese text who wants a sans whose forms read as mainland-standard rather than Japanese, and who is willing to accept a font derived from a Japanese original rather than one designed natively. The README also notes this project is not the same thing as a Magisk module of the same name, a distinction it says it added because some people confused the two.

## What the glyph conversion actually changes

The conversion is not a single pass. The README lists several distinct pieces of work. First, component feet were removed on selected characters to match mainland forms. Second, the Greek and Cyrillic alphabets were redone, and the README says they are now roughly consistent in style with the original font's Latin portion, which the project argues makes them better suited to modern Greek and Cyrillic typesetting. Third, Vietnamese Latin support was added. Fourth, symbol coverage was extended to include the Yijing bagua and sixty-four hexagram symbols, the eighty-one Tai Xuan Jing symbols, mahjong symbols, Chinese chess symbols, counting-rod numerals and the 正 tally-mark character. The font also supports Unicode Variation Sequences for selecting punctuation width and position, with a PDF table linked from the README at documentation/uvs.pdf. The character count is stated as 22,000, including all 20,992 characters of the CJK Unified Ideographs basic block plus scattered characters from Extension A through I. The README says the font includes the 8,105 characters of the Tongyong Guifan Hanzi Biao and adds off-list characters as needed from the ext-characters table.

## The Plus variant and the GB 18030-2022 level 2 target

LXGW Neo XiHei Plus is a separate build. The README states that it completes all characters in CJK Extension A on top of the base font, which brings the character set to the coverage required by GB 18030-2022 implementation level 2. This matters if your encoding target is that standard rather than general Simplified Chinese text. The base font is the right pick for ordinary Simplified Chinese copy; Plus exists for the encoding requirement. The README does not describe how the two builds differ in file size or in how the extra glyphs were drawn, so if you are choosing between them, the coverage statement is what you have to work from. The commented-out section in the README, which is not part of the rendered documentation, describes a longer-term goal of completing the full 20,992-character basic block and the other characters in GBK. Treat that as a stated ambition, not a current property: the README's own visible text puts the count at 22,000 characters.

## Downloading the font and using it in a document

The project does not ship a package manager install. The README lists four download routes: the Releases page on GitHub, the maoken.com page for this font, the zijia.com.cn page, and the Yongshuo netdisk and Lanzou cloud links (the README gives the Lanzou password as gzga). The Releases page is the canonical one, and the most recent release listed is v1.305, dated 2026-08-20. Once you have the font file, installing it is the same as any other desktop font: drop it into your system font directory or use your OS font installer. The commands below are the Linux path, using the standard font directory. Nothing here is project-specific tooling; there is no CLI and no build step for users.

## Where the font does not fit

The README's own maintenance notice is the first limitation. The project describes itself as being in a stable maintenance phase, with work limited to serious defects such as corrupted glyphs or compatibility problems, character additions required by new Unicode releases, and name or metadata updates when brand strategy changes. The README says day-to-day iteration has slowed and that new characters and major changes will be evaluated against Unicode's evolution and actual usage, with no commitment to respond immediately or to accept requests. The last push was on 2026-08-20, so the repository is not dormant, but the scope of what will change is narrow by design. Second, the font is derived from IPAex Gothic and inherits IPA Font License 1.0. The README explicitly warns that anyone planning embedded use should read the licence and the embedding instructions and assess the compliance cost themselves. Third, the character set, while large, is not the full CJK basic block in the base build; if your text includes rare characters outside the covered ranges, you will get fallback. The README does not document a rollback path or version compatibility guarantees for the font files themselves.

## How it compares with the other LXGW families

The related searches around this project point at sibling families: LXGW Neo ZhiSong, LXGW Bright, Yozai Font, and LXGW Marker Gothic. Neo XiHei is the sans (hei) member, derived from IPAex Gothic. The others in the search list are different designs, and the README does not compare them, so the honest difference to state is the source: Neo XiHei's outlines come from a Japanese gothic, and its project is the conversion of those outlines to mainland forms. If you want a Song-style serif, this is not that font. If you want a marker or handwriting feel, this is not that either. Within the same repository, the choice is between the base build and Plus, and that choice is driven by the GB 18030-2022 level 2 coverage requirement rather than by style.

## Licence and the cost of embedding

The repository carries LICENSE.md and a Chinese translation at LICENSE_CHS.md. The GitHub licence field reads NOASSERTION, which means the platform could not classify it automatically; the README states the font follows IPA Font License 1.0 as a derivative of the IPA fonts. The README's important notice singles out embedded use as the case requiring careful reading, and links to a separate embedding instructions document in the lxgw/lxgw repository. That is a real constraint on anyone shipping the font inside an application, an e-book, a PDF with embedded subsets, or a device firmware image. This article cannot tell you whether your specific use is permitted; the README points you at the licence text and the embedding document, and that is the material to check. The practical point is that embedding is the scenario where the licence terms bite hardest, and the project says so up front.

## Maintenance cadence and upgrade cost

Releases are numbered in the v1.30x range, with v1.303 on 2026-06-19, v1.304 on 2026-07-14 and v1.305 on 2026-08-20. That is roughly monthly, which fits the stable-maintenance description: the changes are corrective and additive rather than feature work. Upgrading means replacing the font file. Because the README frames the remaining work as defect fixes, Unicode-driven character additions and metadata updates, an upgrade is unlikely to change the design of existing glyphs, but the README does not promise that. If you pin a font version in a build pipeline, note that the README says the text-format changelog HISTORY.MD is no longer maintained and that release history lives in the Releases page, so your upgrade check is the Releases list rather than a file in the repository. The top-level repository also contains documentation/ and projects/ directories; the README does not describe what projects/ holds.

## Conclusion

Adopt LXGW Neo XiHei if you need a Simplified Chinese sans whose glyph forms follow mainland conventions and whose character set is documented against the Tongyong Guifan table, and if you can accept a font that the README describes as being in a stable maintenance phase where only serious defects, Unicode additions and metadata changes are in scope. Do not adopt it if you need an actively iterating typeface, if you need Traditional Chinese as the primary target, or if you plan to embed the font without reading the IPA Font License 1.0 terms and the embedding instructions the README links to. Before shipping, verify the coverage of the specific characters your text uses, check whether the Plus variant is required for your encoding target, and confirm your embedding use against the licence text.

## FAQ

### How do I install LXGW Neo XiHei?

The README points to four download routes: the GitHub Releases page, maoken.com, zijia.com.cn, and the Yongshuo netdisk or Lanzou cloud links, with the Lanzou password given as gzga. There is no package manager install and no project CLI; once you have the font file, you install it the way your operating system installs fonts.

### What is the difference between LXGW Neo XiHei and LXGW Neo XiHei Plus?

The README states that Plus completes all characters in CJK Extension A on top of the base font, which brings the character set to the coverage required by GB 18030-2022 implementation level 2. The base font is aimed at ordinary Simplified Chinese use, and the README puts its total at 22,000 characters.

### Can I embed LXGW Neo XiHei in an application or document?

The README says the font derives from the IPA fonts and follows IPA Font License 1.0, and it specifically warns that anyone planning embedded use should read the licence and the linked embedding instructions and assess the compliance cost themselves. The repository includes LICENSE.md and a Chinese translation at LICENSE_CHS.md.

### Is LXGW Neo XiHei still being updated?

The README describes the project as being in a stable maintenance phase, with work limited to serious defect fixes, character additions tied to new Unicode releases, and name or metadata updates, and it says there is no commitment to respond immediately to requests. The last push to the repository was on 2026-08-20, and the most recent release listed is v1.305 from the same date.

## Sources

- [Issues](https://github.com/lxgw/LxgwNeoXiHei/issues)
- [lxgw/LxgwNeoXiHei on GitHub](https://github.com/lxgw/LxgwNeoXiHei)
- [README](https://github.com/lxgw/LxgwNeoXiHei/blob/main/README.md)
- [Releases](https://github.com/lxgw/LxgwNeoXiHei/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/lxgw-lxgwneoxihei
