Style Fillable PDF Fonts, Sizes, and Colors

A fillable PDF template is easier to trust when the generated fields look like part of the original document. Font family, point size, and color all affect that trust. A certificate, intake form, permit, or internal worksheet can technically be filled while still looking wrong if typed values are too large, too small, or visually disconnected from the rest of the form.

DullyPDF treats those choices as template appearance settings, not as one-time preview tweaks. The operator can choose a global field appearance for the workspace and then override individual text or date fields when a specific field needs a different font, size, or color.

The left field panel gives operators a global starting point for text and date fields. The global editor can set the shared font family, keep font size on Auto dynamic sizing, and choose one field color that inherited fields reuse across preview and export.

That global layer keeps setup fast. Most recurring forms only need one appearance rule, so teams can avoid setting every field manually while still producing editable and flat downloads that match the chosen template style.

• Use Default (Helvetica) when the template should behave like previous DullyPDF exports.
• Use Auto font size when field height should drive the rendered text size.
• Use global font color when most fields should share the same visible text color.

Some PDFs need targeted exceptions. A narrow ID field may need a smaller point size, a highlighted total may need a specific color, or a section heading may need a bold font from the supported Base 14 set. The field inspector lets text and date fields inherit the workspace appearance or store their own override for font, font size, and color.

Those overrides travel with the field metadata. They are used in the live fill preview, saved templates, editable PDF downloads, flat PDF downloads, Fill By Link materialization, and API Fill materialization.

The important product behavior is persistence. When a user saves a DullyPDF template, the selected font, font size behavior, and font color choices are saved with the field definitions. Reopening the template should not collapse custom colors back to black or forget which fields intentionally inherit the global color.

The same rule applies after publication. A saved template used for Fill By Link or API Fill keeps the selected field colors when DullyPDF generates a fillable form output from respondent answers or JSON data.

Editable exports keep the value inside the AcroForm field and attach widget appearance data so the completed value is visible when the PDF opens. The editable export should also apply the selected font color and size while the user is typing in the selected field, then keep the same appearance once the field is committed.

Flat exports remove interactivity and draw the final value into the page content. Those output modes are different, but they should both respect the same saved font, size, and color decisions.

That distinction prevents the bug where a PDF shows text on the page but the actual editable field remains empty or uses a stale default appearance. DullyPDF avoids that by treating editable output as real field data plus field appearance, not a flat drawing with an empty widget layered on top.

PDF viewers are not completely uniform while a user is actively typing inside an exported field, so focused font-family behavior can still vary by viewer. DullyPDF writes the field appearance so selected color and size apply to the editable typing state where supported, and the committed value, printed output, and flat output follow the selected DullyPDF appearance.

For normal text and date fields, DullyPDF uses the text-safe Helvetica, Times, and Courier Base 14 families because those fonts can be referenced without embedding external font programs. Symbol-only Base 14 fonts are intentionally excluded from typed field controls because normal user text does not map reliably to those encodings across common viewers.