Recommended Free Tools
A “missing” value in a generated PDF can originate in the source record, the field mapping, the template, the export process, the form state, or the PDF viewer. There is no honest single fix without knowing which workflow produced the file. First identify whether you used a template-and-JSON generator, Word/Office export (including Acrobat PDFMaker), or a fillable PDF form. Then test the handoff where the value disappears.
Start by identifying how the PDF was made
Write down the product, template format, input source, export method, PDF viewer, and what “not showing” means. A blank merged field, a leftover placeholder, missing comments, and an empty interactive form field are different failures.
| Workflow | What should appear in the PDF | First place to check |
|---|---|---|
| Template/API generation | Text, tables, images, or conditional sections merged from structured data | Source value, JSON property, template tag, and generation request |
| Word or Office export/PDFMaker | Content visible in the source document, converted into fixed PDF page content | Source document and conversion settings |
| Fillable PDF form | Interactive field values, which may not be flattened into page text | Field value, appearance, save/submit state, and viewer |
Also open the same file in another trusted PDF viewer. That comparison can show whether the value is absent from the file or merely not rendered by one viewer; it does not, by itself, prove that a particular viewer is defective.
Template-and-JSON generation: trace every handoff
Adobe describes its Document Generation API this way: “During the Document Generation Process, the Document Generation API replaces the template tags in the document template with the input data to generate the output document.” In practical terms, the value must survive each link in this chain:
#1 Best Overall
- Source record: Confirm the value exists, is not null, and has the expected type.
- Mapping: Confirm the property name and nesting match the data model exactly, including capitalization.
- Request payload: Log the JSON actually sent to the generator, not merely the object before serialization.
- Template tag: Inspect the Word template for the exact tag, conditional block, and any spelling or nesting difference.
- Generated artifact: Check whether the value is absent, replaced by a default, or present but visually hidden.
Check defaults and optional tags
Adobe documentation says that when a specified tag is not present in the input JSON, its placeholder is replaced with the tag’s default value. A blank default therefore looks like missing data even though generation succeeded. Set an explicit, recognizable test value such as TEST-123 and generate a minimal document containing only that tag. If the test appears, the problem is in the larger payload, conditional logic, or source mapping.
An Adobe Community question uses the wording “When field not found in body the variable is left in document.” A community-manager reply discusses blank values and default or optional tags, but the behavior is setup- and version-specific rather than a universal rule. Treat a leftover placeholder as evidence to inspect the current API behavior, tag configuration, and exact payload—not as proof that every Adobe document-generation request behaves the same way.
Use a minimal mapping test
Create a reduced template with one plain text tag and one known value. Remove conditional sections, repeating tables, formatting, and images. Generate it with the smallest valid request. Then add the original sections back one at a time. This separates a naming problem from a malformed block or a conversion problem.
Check conditional content and formatting
A value can be present but omitted by a condition, placed in a hidden run, rendered in white text, or pushed outside a page boundary. Search the source template for the tag in the document’s editing view, not only in its visual preview. Confirm that the condition tests the same data type you send (for example, boolean versus the string "true").
Free tools Windows power users keep installed
One-click scans. No signup required.
Word export and Acrobat PDFMaker: distinguish data from markup
If the “data” is a Word comment or tracked change, it is not ordinary field merging. Adobe’s support guidance, updated March 3, 2026, states that Word PDFs exported with PDFMaker have omitted tracked changes and comments since December 2025, regardless of the Review-tab markup settings. The documented Windows workaround is to set the registry value bEnableMarkupExport to 1 under the applicable Acrobat PDFMaker Word key, then restart Word. This is specifically for Word markup; it is not a general repair for a missing merged field.
Registry edits affect Windows configuration. Export the relevant key or create a restore point according to your organization’s policy before changing it, and use the key for your installed Acrobat/Office version. If you cannot use the registry, export a copy through another conversion path and compare the results.
Isolate PDFMaker settings
For broader PDFMaker failures, Adobe recommends isolating conversion settings and checking whether another method—such as the Adobe PDF printer or Distiller—succeeds. If an alternate method retains the content while PDFMaker does not, investigate PDFMaker features and settings rather than changing the source data first. Compare the source document and resulting PDFs page by page, including headers, footers, fields, comments, and tracked changes.
Fillable PDFs: an interactive value is not the same as printed text
A fillable PDF contains fields that collect data; a generated report may instead contain fixed page content. Adobe documents creating fillable forms from Word files or scanned documents and using different field types. Ask three questions:
- Is the value in the field’s stored value, or is the field merely displaying its default?
- Was the form saved or submitted after the value was entered?
- Are you expecting an interactive field to become ordinary, selectable page text (flattening)?
Some viewers display a field’s appearance differently from its stored value. Open the file in another trusted viewer and inspect the field properties with a PDF tool that can reveal form data. Do not assume that printing or exporting a form automatically preserves editable values; verify the output required by your workflow.
Rank #4
A practical diagnostic sequence
- Record the workflow. Note the generator, template, input source, export route, viewer, and the exact missing item.
- Verify the source. Display the original record or document and confirm the value is populated and spelled as expected.
- Inspect the handoff. For JSON, log the serialized request and check property names, nesting, nulls, and data types.
- Test the template. Replace the expected value with a distinctive known value in a minimal template. Check tags, defaults, and conditions.
- Compare conversion routes. If source content exists but the PDF does not, try the documented alternate conversion method and compare files.
- Check form state. For interactive PDFs, verify stored field values, save/submit status, and whether flattening is required.
- Compare viewers. Open the same file elsewhere to separate a rendering issue from missing PDF content.
- Preserve evidence. Keep the source, payload, template version, export settings, generated PDF, and viewer/version together so a repeatable difference can be found.
Common symptoms and targeted fixes
| Symptom | Likely branch | Action |
|---|---|---|
| Blank field, no error | Missing property or blank default | Log the payload; inspect the tag’s default and run a known-value test. |
| Placeholder remains literally | Tag was not resolved or behavior is setup-specific | Verify exact tag syntax, current API documentation, optional/default settings, and payload mapping. |
| Comments or tracked changes disappear | PDFMaker markup omission | Apply Adobe’s dated PDFMaker guidance, including bEnableMarkupExport=1 where appropriate, or compare another export route. |
| Field appears empty in one viewer | Form appearance or viewer rendering | Inspect stored field data and open the same file in another viewer. |
| Section is missing but other fields work | Conditional block, malformed repeat, or hidden formatting | Reduce the template to one tag, then reintroduce the block incrementally. |
Or skip the browser setup
If your workflow needs a clean screenshot of the source web page before or alongside PDF generation, ScreenshotNeo provides a one-request capture API. It accepts consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; bot checks, blank pages, timeouts, failed loads, and cache hits are not billed. Responses identify the result with X-Page-Verdict and X-Billed headers. Its MCP server lets Claude, Cursor, and other MCP clients use take_screenshot, get_page_info, and capture_pdf.
See the ScreenshotNeo API documentation for options such as full-page capture, CSS-selector elements, custom JavaScript, waiting for network idle or a selector, headers and cookies, PDF page ranges, caching, and bulk capture.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Create a free ScreenshotNeo account to try it.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Cost, reliability, and repeatability notes
- Do not regenerate blindly: preserve the failing payload and template so each test changes one variable.
- Use a distinctive test value and a minimal document to reduce time spent inspecting large reports.
- Record product and version information, especially for export behavior that changed in December 2025.
- Validate both content and presentation: a value can be stored correctly yet hidden by a condition, formatting, field appearance, or viewer.
Frequently Asked Questions
Can the PDF itself prove where the value was lost?
Usually not. Compare the source record, serialized payload, template, generated artifact, and viewer; the PDF shows the final state, not every earlier handoff.
Why does a missing JSON property sometimes produce an empty field?
In Adobe Document Generation, Adobe says an absent tag in the input JSON is replaced with that tag’s default value. If the default is blank, the result looks like missing data.
Is the PDFMaker markup setting a fix for merged fields?
No. Adobe documents it for Word comments and tracked changes omitted by PDFMaker exports since December 2025; ordinary template/API fields require separate mapping and tag checks.
The Bottom Line
Find the first stage at which the value disappears—source, payload, tag/default, conversion, form state, or viewer—then fix that stage and rerun a minimal known-value test.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
