Tegaki: animated handwriting from any font, with caveats
Handwriting animation for the web. Supports any font or text.
At a glance
- What is it?
- Tegaki turns a font into a stroke-by-stroke handwriting animation through a React component or a single npx command. The trade-off is that its bundled fonts cover ten scripts, and everything else goes through a web studio.
- Who is it for?
- Tegaki suits teams that want self-drawing text in a React, Svelte, Vue, Solid, Astro, or vanilla app and are happy with the ten bundled font families; its CLI also covers one-off SVG needs. It is the wrong tool if you need PNG, GIF, or WebM output from the command line, since the README says the CLI emits SVG only and points to the interactive studio for those formats.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 17 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 21, 2026, and from our analysis. They are not legal advice.
Star history
- gkurt/tegaki3,331 ★ · +232
| Repository | 2026-09-24 | 2026-11-21 |
|---|---|---|
| gkurt/tegaki | 3.1k | 3.3k |
232 Stars in the last 58 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What problem Tegaki solves, and who it is for
Drawing text as if a hand were writing it normally means authoring stroke paths by hand, one glyph at a time. Tegaki's README states the project's premise directly: it "turns any font into animated handwriting" with "no manual path authoring" and "no native dependencies." The input is a font, not a set of coordinates.
The audience is front-end developers who want a handwriting effect inside a component tree. The README lists adapters for React, Svelte, Vue, SolidJS, Astro, Web Components, and vanilla JavaScript, so the same renderer can be dropped into most modern stacks. A second audience is people who just want a self-drawing SVG file for a README or a slide deck: the CLI path requires no project setup at all. The npm package name is tegaki, and the repository is a Bun workspace with packages/, examples/, and e2e/ directories.
How the renderer turns a font into strokes
The README does not document the internals, but the repository layout gives two clues. The root package.json lists harfbuzzjs as a dependency, and harfbuzz is a text shaping engine, which is the step that maps a string plus a font to positioned glyphs before anything can be drawn. The README's phrase "no native dependencies" is consistent with that choice: harfbuzzjs is the JavaScript build of HarfBuzz, so it runs without a compiled addon. The second clue is the font packaging. Bundled fonts are imported as modules, for example tegaki/fonts/caveat, which means the data a renderer needs travels with the import rather than being fetched from a font file at runtime.
The public surface is small. TegakiRenderer takes a font and renders children; TegakiEngine is the core entry point for vanilla JavaScript. The README does not describe the animation timing algorithm, so any claim about how stroke order or pacing is computed would be guesswork.
Installing Tegaki and drawing your first line
The README's quick start is two steps. Install the package from npm:
npm install tegakiThen render it. The README's React example imports the renderer and a bundled font, and passes the text as children. After this renders, the text should draw itself stroke by stroke, which is the behaviour the README describes.
import { TegakiRenderer } from 'tegaki';
import caveat from 'tegaki/fonts/caveat';
function App() {
return (
<TegakiRenderer font={caveat} style={{ fontSize: '48px' }}>
Hello World
</TegakiRenderer>
);
}If you do not want a component, the README gives a CLI path that needs no install. Running it writes a self-drawing, looping SVG named after the text:
npx tegaki "Tegaki is awesome"The README shows the options for font, mode, output, stagger, size, and color. Note the quoting: the text is a single argument, and --color takes a hex string.
npx tegaki "Hello World" --font tangerine --mode once -o hello.svg
npx tegaki "ABC" --stagger 80% --size 140 --color "#222"--mode accepts loop (the default), once, or static. Run npx tegaki --help for the full option list and --list-fonts for what ships in the box.
The font list is the real boundary
Tegaki bundles ten handwriting families: Caveat, Italianno, Tangerine, Parisienne, Suez One, Amiri, Tillana, Klee One, Nanum Pen Script, and Atma. Their script coverage is uneven and worth reading closely. Six are Latin. Suez One adds Hebrew, Amiri adds Arabic, Tillana adds Devanagari, Atma adds Bengali, Nanum Pen Script adds Korean Hangul syllables and jamo, and Klee One covers Japanese kana plus Kyōiku grade 1 and 2 kanji.
That last entry is the sharpest limitation. Grade 1 and 2 kanji is a school-level subset, not the full jōyō set, so a Japanese sentence containing anything above that level will not be covered by the bundled font. The README's answer for everything outside this list is the interactive studio at gkurt.com/tegaki/studio/, described as the way to "create a custom bundle." That is a browser workflow, and the README does not describe a headless or command-line path for generating a custom font bundle. If your build pipeline needs to regenerate a font automatically, the documented route does not cover it.
SVG only from the CLI, and what that rules out
The CLI is the fastest way to get an animated result, and it is also the most constrained. The README says plainly that "the CLI emits SVG only" and directs anyone who needs PNG, GIF, or WebM to the interactive studio. So a script that wants a rasterised or video output has no documented command-line path; the studio is a manual step.
There is a second constraint in the same paragraph: the CLI writes a looping SVG by default. For a README badge or a landing page that is probably what you want, but for a one-shot reveal you have to remember --mode once, and for a still image --mode static. Neither of those is the default, which is a small thing that will surprise anyone who runs the bare command and then wonders why the drawing restarts.
A third point is that the default output filename is derived from the text. The README's example writes tegaki-is-awesome.svg. Text with characters that do not survive filename conversion is a case the README does not address; use -o explicitly when the string is not plain ASCII.
Alternatives and where the approach differs
The closest comparison in the README itself is not another library but the manual approach: authoring SVG paths or stroke data by hand. That gives total control over stroke order and pacing, and it is the only way to get genuinely correct stroke order for a script where the conventional order matters. Tegaki's selling point is that it removes that authoring step entirely, at the cost of whatever ordering the font's outline data implies. If correct pedagogical stroke order is the requirement, hand-authored paths remain the safer choice.
Among the integrations the README lists, Remotion is the more interesting contrast. Remotion builds video programmatically with React, and the README links a Tegaki integration example in its repository. The two are not competitors so much as layers: Remotion handles frames and encoding, Tegaki handles the drawing. If your output is a video file rather than an SVG, that combination is the documented route, and it sidesteps the CLI's SVG-only limitation.
Maintenance, licence, and upgrade cost
The last push to the repository was on 2026-09-23, and the most recent release is [email protected] from the same day, following 0.22.1 and 0.22.0 on 2026-07-12. The version number is still in the 0.x range, which is worth weighing: the README's public API is small (TegakiRenderer, TegakiEngine, registerTegakiElement, and the font imports), so the surface that could break is narrow, but a 0.x project makes no compatibility promise through its version number.
The licence is MIT, stated in the README and present as a LICENSE file at the repository root. MIT permits commercial use and modification; it requires the copyright notice and permission notice to be retained, and it provides the software without warranty. That is the extent of what the licence text says, and it is not legal advice.
The repository is a Bun workspace, and the root package.json shows the toolchain: Bun for running scripts, Biome for linting and formatting, husky for git hooks, and a typecheck script built on tsgo. The published package is the tegaki workspace inside packages/, so consuming it from npm does not pull in that toolchain. Contributors would need Bun and the workspace scripts (bun run checks chains check, typecheck, and test).
Editorial conclusion
Tegaki suits teams that want self-drawing text in a React, Svelte, Vue, Solid, Astro, or vanilla app and are happy with the ten bundled font families; its CLI also covers one-off SVG needs. It is the wrong tool if you need PNG, GIF, or WebM output from the command line, since the README says the CLI emits SVG only and points to the interactive studio for those formats. Before adopting it, check whether your target script is in the bundled list and whether the studio's generated bundle is something you can commit to your repository, because the README does not describe a build step for custom fonts.
Frequently asked questions
How do I install Tegaki in a React project?
Run npm install tegaki, then import TegakiRenderer from 'tegaki' and a bundled font such as tegaki/fonts/caveat. Pass the font as the font prop and the text as children, as the README's quick start shows.
Which fonts does Tegaki bundle?
The README lists ten: Caveat, Italianno, Tangerine, Parisienne, Suez One, Amiri, Tillana, Klee One, Nanum Pen Script, and Atma. Their coverage spans Latin, Hebrew, Arabic, Devanagari, Bengali, Japanese kana and grade 1 to 2 kanji, and Korean Hangul.
Can the Tegaki CLI produce a PNG or a video?
No. The README states that the CLI emits SVG only and points to the interactive studio for PNG, GIF, or WebM output.
What does the Tegaki CLI do if I do not pass --mode?
It uses loop, so the SVG repeats forever. The other two values are once for a single draw and static for the finished artwork.
Official sources
Where developers are discussing it
Posts on Hacker News, dev.to and Lobsters that link to this repository, found by our scan of those communities. 0 in the last 30 days; newest first.
- Handwriting Animation for the Web [Multilingual]Hacker News · Oct 15, 2026 · 1 points · 1 comments
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/gkurt-tegaki)Star history chart for your README
[](https://hysenlabs.com/projects/gkurt-tegaki)Was this useful?