Help

Find the shortest Alphabit Studio guide for creating, editing, saving, importing, exporting, or recovering a bitmap font.

Choose what you are trying to do. Each guide keeps the main workflow short, then explains the details and recovery paths that matter for that task.

Start here

Getting startedThe shortest complete route from an empty workspace to export.

Use the editor

Workspace and windowsHow font, editor, preview, and shared utility windows fit together.Edit glyphsDraw and adjust characters while testing them in live specimen text.

Files and recovery

Import and exportFormat support, conversion expectations, and the safest source format.Save and recover workWhat is saved locally, what is portable, and how to recover safely.

How the editor works

  • The app uses a floating multi-window workspace and can keep multiple fonts open at once.
  • Each font gets its own Characters window and one or more editor or preview windows.
  • The editor model is bitmap-first: glyph pixels and shared font metrics are the source of truth.
  • Imports normalize source formats into that internal model, so some format-specific metadata is preserved and some is flattened.
  • `.alphabit.json` is still the full-fidelity source format for continued editing.

Need something specific?

If you are evaluating format support in detail, start with Import and export fonts. That page carries the public-facing support matrix and the main round-tripping notes.

For general use, the main split is simple:

  • `.alphabit.json` is the editable source-of-truth format.
  • Bitmap imports are normalized into the editor’s shared bitmap model.
  • Some exports are intentionally lossy because the target format is simpler than the editor model.

Get in touch

If you have questions or want to share feedback, send an email to contact@alphabit.studio or follow @alphabit.studio on Bluesky for updates and announcements.