Save 4 hours! We auto-setup your workflow! Free!

Drop your workflow.json — we handle every dependency, custom node, and model. Just open the link and run.

Auto-Setup Workflow Json (Free) Now!
ComfyUI > Nodes > OpenKatana > OpenKatana · Preview fonts

ComfyUI Node: OpenKatana · Preview fonts

Class Name

OpenKatana_preview_fonts

Category
OpenKatana/Tools
Author
rk0neki (Account age: 235days)
Extension
OpenKatana
Latest Updated
2026-11-05
Github Stars
0.05K

How to Install OpenKatana

Install this extension via the ComfyUI Manager by searching for OpenKatana
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter OpenKatana in the search bar
After installation, click the Restart button to restart ComfyUI. Then, manually refresh your browser to clear the cache and access the updated list of nodes.

Visit ComfyUI Online for ready-to-use ComfyUI environment

  • Free trial available
  • 16GB VRAM to 80GB VRAM GPU machines
  • 400+ preloaded models/nodes
  • Freedom to upload custom models/nodes
  • 200+ ready-to-run workflows
  • 100% private workspace with up to 200GB storage
  • Dedicated Support

Run ComfyUI Online

OpenKatana · Preview fonts Description

Renders local fonts in a visual comparison sheet with metadata and character coverage checks.

OpenKatana · Preview fonts:

OpenKatana_preview_fonts creates a visual comparison sheet from local font files so you can judge how different typefaces look before choosing one for your artwork or motion-design project. It renders actual font outlines with Pillow rather than approximating their appearance or identifying fonts from reference images. Each specimen includes the font’s family and style, followed by the same sample wording in a pink-red color on a dark background. The comparison starts at a consistent font size and reduces oversized specimens to help longer text fit within the sheet. It also records font metadata and checks character coverage, helping you spot fonts that may lack characters needed for your design. This is a practical tool for comparing letterforms, readability, and visual tone, but it is not a substitute for checking final browser-based layout, animation, or glow effects.

OpenKatana · Preview fonts Input Parameters:

project_id

A required STRING passed to the tool’s argument-building helper to provide project context for the operation. Supply the identifier associated with the project you intend to work with. The supplied code does not show how project identifiers are created, validated, or used to resolve paths, so it does not establish whether this operation creates or modifies project records. No default value, minimum or maximum length, or list of permitted values is shown in the supplied node interface.

arguments

A required STRING containing the tool arguments, processed by the shared argument-building and typed-argument helpers before the preview operation is invoked. This is the node’s general argument entry point; font selection and specimen configuration are not exposed as separate node sockets. The underlying preview implementation works with a collection of font-file paths, sample text, and an output directory, internally named sources, text, and out. It requires 1–8 font files, accepts only .ttf, .otf, and .ttc extensions regardless of letter case, and requires sample text to be a string containing 1–120 characters. Its output directory must not already exist. These are preview-operation requirements, not length limits on the arguments STRING itself. The supplied code does not include the argument parser or tool signature, so the exact accepted JSON structure, path-resolution rules, and any automatically supplied directory values cannot be confirmed here. Use the tool’s documented argument schema rather than assuming these internal names alone define a complete payload. No default value or overall string-length range is shown for this input.

after

An optional STRING accepted by the shared node interface. The execution method gives it a default value of None, meaning it can be omitted. Although its name may suggest an execution-order or dependency role, the supplied method does not read it, pass it to the argument helpers, or forward it to the tool invocation. Consequently, no direct effect on font selection, rendering, or returned results is established by this code. No permitted-value list or minimum or maximum string length is shown; do not rely on it alone to guarantee sequencing without checking the wider OpenKatana workflow behavior.

OpenKatana · Preview fonts Output Parameters:

result_json

A STRING containing the tool response after it has been processed by the shared response helper. The underlying preview function returns a fonts list, a preview_images list, and a note; the supplied code does not show whether the response helper adds an outer envelope around those values. Each entry in fonts records the font-file path, its family and style, a sha256 file fingerprint, natural_width_at_70px, and missing_glyphs. The fingerprint helps distinguish the actual files used, while the width records the sample’s measured width at the original 70-pixel font size, even if the displayed specimen was subsequently reduced. missing_glyphs contains characters identified as absent from the font; an empty string indicates no missing characters were reported, whereas null means coverage could not be determined. preview_images contains the path to the saved fonts.png comparison sheet, rather than a directly connectable ComfyUI IMAGE output. The sheet is 1000 pixels wide and 160 pixels tall per font, giving a height of 160–1280 pixels for the supported number of specimens. The accompanying note explains that the preview uses actual local font outlines rendered with Pillow and recommends timeline previews for verifying browser layout, animation, and glow.

OpenKatana · Preview fonts Usage Tips:

  • Compare fonts using identical wording that resembles your final design. Include the uppercase letters, lowercase letters, numbers, punctuation, and accented characters you actually need, while keeping the sample within 1–120 characters.
  • Use 1–8 fonts per comparison. The supplied order determines the top-to-bottom order of specimens, so place your strongest candidates next to each other for easier visual comparison.
  • Keep sample text short when judging relative size and letterform details. Rendering begins at 70 pixels; if a specimen measures more than 950 pixels wide, the node reduces its font size using a proportional calculation, with a minimum of 8 pixels. Long wording can therefore make different fonts appear at different sizes.
  • Check missing_glyphs alongside the image, especially for multilingual designs. A null result means coverage is unknown, not that every character is supported; even a successful coverage check does not guarantee correct shaping or final browser appearance.
  • Use supported local .ttf, .otf, or .ttc files. This preview function does not accept .woff or .woff2 files, even though other OpenKatana font features may support them.
  • When choosing a TTC collection, expect the first face: the implementation loads the file without selecting a different collection index. Use a separate font file when you need to compare another specific face.
  • If the tool’s argument schema lets you choose the output directory, select a new directory for every run. The preview function creates that directory with existing-directory reuse disabled.
  • Open the image referenced by preview_images to inspect the sheet, then verify your chosen font in a timeline preview before finalizing browser-based placement, animation, or glow.

OpenKatana · Preview fonts Common Errors and Solutions:

Supply 1..8 font files and 1..120 characters

  • Explanation: This validation error occurs when the source collection has fewer than one or more than eight entries, the sample text is not a string, or the sample is empty or longer than 120 characters.
  • Solution: Supply 1–8 font files and a text string containing 1–120 characters. If you need to compare more fonts or longer wording, split the task into multiple previews.

Font specimens require TTF, OTF or TTC

  • Explanation: At least one selected file has an extension other than .ttf, .otf, or .ttc. Extension matching is case-insensitive, but formats such as WOFF and WOFF2 are not accepted by this function.
  • Solution: Select a supported font file. If you only have another format, obtain a legitimate TTF or OTF version; changing the filename extension does not convert the font.

Cannot load font: [font path]

  • Explanation: Pillow could not load the indicated font, and the preview function converted that loading failure into this error. Possible causes include an incorrect path, a missing or unreadable file, or damaged or unsupported font data.
  • Solution: Confirm that the path points to an accessible font file on the machine running OpenKatana. Check file permissions and try opening the file with another font viewer or testing a known-good TTF or OTF file.

FileExistsError: [Errno 17] File exists

  • Explanation: The output directory already exists. The implementation deliberately creates it with exist_ok=False, so it does not reuse an existing folder.
  • Solution: Choose a new output directory through the supported argument configuration, if available. If a failed attempt already created the folder, use another location or remove only that disposable folder after checking its contents.

PermissionError: [Errno 13] Permission denied

  • Explanation: The operating system may prevent OpenKatana from reading a font, creating the output directory, or saving fonts.png. Exact wording and error wrapping depend on where the failure occurs.
  • Solution: Use font locations readable by the running application and an output location where it can create folders and files. In hosted or containerized installations, confirm that the relevant folders are accessible inside the runtime environment.

unexpected inputs: [input names]

  • Explanation: The node explicitly raises this TypeError when execution receives extra keyword fields not included in its declared tool inputs. Font settings should not be added as arbitrary node sockets.
  • Solution: Use the exposed project_id, arguments, and optional after inputs. Put tool-specific settings into arguments according to the supported schema rather than supplying undeclared keyword inputs.

Argument parsing or validation failure: exact message depends on the shared helpers

  • Explanation: The node processes arguments before invoking the preview function. An incorrectly formatted argument string or a payload that does not match the tool’s schema may fail at this stage; the supplied context does not include the parser’s exact error messages.
  • Solution: Check the documented signature for this tool and validate the argument format it expects. If that format is JSON, check quotation marks, commas, and value types, and remember that the internal function signature alone does not establish the complete external payload structure.

OpenKatana · Preview fonts Related Nodes

Go back to the extension to check out more related nodes.
OpenKatana
RunComfy
Copyright 2025 RunComfy. All Rights Reserved.

RunComfy is the premier ComfyUI platform, offering ComfyUI online environment and services, along with ComfyUI workflows featuring stunning visuals. RunComfy also provides AI Models, enabling artists to harness the latest AI tools to create incredible art.

OpenKatana · Preview fonts