Commercial workflow page
Learn how AcroForm /DA, /DR, /AP, and /V keep field values, fonts, sizes, and colors inside editable PDF widgets after export.
A fillable PDF is not just a visual page with rectangles on top. The PDF catalog owns an /AcroForm, the form owns logical field dictionaries, pages own widget annotations, and widgets can own appearance streams that describe how the filled value should look.
That split matters because the user-visible text and the editable field value are not the same thing. If an exporter only draws text onto the page while leaving an empty widget above it, the PDF can look filled but behave like an empty form when someone clicks, edits, submits, or imports it later.
For text-like editable output, the current value belongs in the field dictionary as /V, with /DV used when the generated file should also treat that value as the default reset state. That is what lets a downloaded editable PDF reopen with the text inside the actual field.
Flat output is different. A flat PDF should draw the final value into page content and remove interactive widgets. Mixing those models creates duplicated or stale values, so DullyPDF keeps editable output and flat output as separate export paths.
Variable text fields use a default appearance string, usually called /DA, to describe the font resource, point size, and text color. A typical value looks like /Helv 10 Tf 0 0 0 rg: use the Helv font resource at 10 points with RGB black text.
DullyPDF writes selected fonts, Auto or custom font sizes, and global or field-specific colors into appearance data so editable fields can display both active typed text and the final committed value with the intended style instead of falling back to a generic viewer default.
The font name inside /DA is a resource alias. It only works reliably when the corresponding font resource exists in the document-level /AcroForm /DR /Font dictionary or in field/widget resources. DullyPDF registers the selected text-safe Base 14 font resources so appearance strings and widget appearances can resolve them.
DullyPDF uses short AcroForm-style aliases such as /Helv, /Time, /TiIt, and /CoBo while the underlying /BaseFont remains Helvetica, Times, or Courier. This keeps generated files closer to common AcroForm conventions.
A widget appearance stream is a small PDF drawing program attached to a form widget. For text fields, the normal appearance draws the current value with the chosen font, size, and color. For checkboxes and radio buttons, the normal appearance usually contains state names such as /Off and the selected export value.
An appearance stream is still part of the field. It is not the same as flattening. Editable PDFs can and should include widget-owned /AP data when that helps viewers show the completed form immediately after download.
DullyPDF saves normalized appearance intent with the template field metadata and writes the corresponding PDF keys during materialization. Global editor settings provide the inherited default, and the individual field inspector can override that default for a specific widget. That is why fonts, font sizes, and field colors can persist through save, reopen, Fill By Link, API Fill, editable download, and flat download.
Generated editable PDFs also carry compact DullyPDF appearance metadata so re-uploading one of those files can restore global color and field-specific color overrides in the inspector rather than treating every color as an unrelated PDF default.
Viewers have latitude while a user is actively focused inside a field. Adobe, Chrome, Preview, and browser PDF engines can differ in how much of the live typing state they source from /DA before the value is committed. That does not change where DullyPDF stores the chosen appearance: field values stay in /V, appearance lives in /DA and widget /AP, and flat exports bake the final visible state into page content.
The practical QA check is to inspect both editable and flat outputs. Editable output should keep values inside fields and show the selected appearance when the field is not being actively edited. Flat output should have no live widgets and should visually match the selected fonts, sizes, and colors.
Need deeper technical details about acroform field appearance? Use the Rename + Mapping docs and Search & Fill docs to validate exact behavior.
/DA is the default appearance string for variable text fields. It references a font resource, point size, and text color.
/AP is the appearance dictionary for a widget annotation. Its normal appearance can draw the current field value or the selected checkbox/radio state.
That creates a PDF that looks filled but has a different live field value above the drawn text. Editable exports should put the value and appearance into the AcroForm field itself.
DullyPDF saves normalized appearance metadata with the template and writes the selected color into field/root appearance strings and widget appearances when generating PDFs.
These walkthroughs and comparison posts cover the same workflow cluster from an operator point of view, which helps you move from a route summary into a more specific implementation path.
Use these docs pages to verify the exact DullyPDF behavior behind acroform field appearance before you ship it as a repeat workflow.
These adjacent workflow pages cover nearby search intents teams compare while evaluating acroform field appearance.
