Skip to content
+

Support

How to report issues efficiently and what information helps diagnose faster.

Before reporting

  • Confirm the input file format and extension.
  • Reproduce once with a single font loaded when the issue is about browsing, subset, conversion, or Text to SVG.
  • If the issue is in Font Builder, note whether you were creating a new font or editing a source font.
  • Run Preflight Check and keep the report text if the issue involves SVG glyph import or font building.
  • Note whether the issue happens in Text to SVG, Font Builder, Preflight Check, Subset Font, Web Package, Format Conversion, or Asset Export.

What to include in a report

  • macOS version
  • WebFont version
  • Source font format (ttf / otf / woff / woff2)
  • SVG sample characteristics if Font Builder is involved (outlined paths, live text, raster images, masks, filters, scripts, animation, or external resources)
  • Whether a .webfontproject file is involved
  • Exact steps to reproduce
  • Actual result and expected result
  • Full error/warning text shown by the app

Where to reach

Providing precise reproduction steps and warning text usually shortens turnaround time.