Introduction - How to Use LetterLab

Modern typography for the creative industry

Overview

LetterLab provides a centralized repository for variable fonts, static masters, and web-ready WOFF2 packages. Our platform handles font subsetting, hinting optimization, and cross-browser rendering consistency out of the box.

We operate on a tiered licensing model tailored for studios and enterprise teams. The Base tier covers up to 5 active web domains and includes standard OTF/TTF exports. The Studio tier unlocks unlimited web deployments, access to our dedicated @font-face CDN, and priority support for custom axis interpolation. All licenses are perpetual with optional annual maintenance for font updates and security patches. For web integration, ensure your build pipeline supports standard CSS @font-face declarations and that your server headers include font-display: swap to prevent invisible text during load. We recommend preloading critical weights via link rel="preload" in your document head.

Quick Links

Getting Started

Installation & Setup

Configure your environment variables, generate API keys, and pull your first font package via npm or direct CDN endpoints.

Read Guide

Integration

Web & CMS Plugins

Step-by-step instructions for WordPress, Shopify, and custom React/Vue implementations using our JavaScript SDK.

View Code Snippets

Support

License Verification

Manage your active domains, generate audit reports, and update your organization's user access controls.

Open Dashboard

Versioning

We follow semantic versioning for all font families and SDK releases. Major updates introduce new axes or OpenType features, minor updates add character sets or fix kerning pairs, and patch releases address rendering bugs.

Current stable release: v2.4.1 (released October 12, 2024). The v3.0 beta introduces native CSS font-palette support and improved Latin Extended-B coverage. Check our changelog for migration notes when upgrading from v1.x to v2.x. All legacy static masters remain available in the archive vault for backward compatibility. Dependencies are documented in each package's package.json or composer.json manifest.