Jumbled content in PandaDoc is caused by conflicting source formatting, broken tokens, incompatible paste formatting, or template structure errors. Fix it by stripping external formatting before import, auditing token logic, rebuilding affected content blocks, and standardizing your template library so the problem does not repeat.

If a PandaDoc document has ever sent to a client or new hire looking like a formatting disaster — misaligned fields, scrambled paragraphs, broken merge tags — you already know the cost. Documents stall. Signers lose confidence. HR teams spend hours troubleshooting instead of onboarding.

This guide covers the nine most effective fixes, from quick patches to structural prevention. Before you dig in, it helps to understand where these formatting problems most often live — which is covered in depth in the 9 PandaDoc Templates Every HR Team Needs for New Hire Onboarding resource. Teams dealing with onboarding bottlenecks more broadly will also want to review 7 Onboarding Bottlenecks PandaDoc Automation Eliminates and the 11 Onboarding Documents to Automate With PandaDoc First checklist.

What Causes Jumbled Content in PandaDoc?

Before applying a fix, identify the source. Jumbled content in PandaDoc falls into four categories:

Fix 1: Strip All External Formatting Before Pasting

The most common cause of jumbled content is pasting text from Microsoft Word or Google Docs directly into PandaDoc. Both applications carry hidden formatting tags that override PandaDoc’s native styles.

What to do: Before pasting any content into a PandaDoc block, first paste it into a plain-text editor (Notepad on Windows, TextEdit in plain-text mode on Mac). Then copy from there and paste into PandaDoc. This strips the source application’s formatting entirely.

For bulk content migrations — such as moving a large offer letter library into PandaDoc — do this for every content block, not just the body paragraphs. Headers, bullet lists, and signature blocks all carry hidden styles that can collide.

This single step eliminates the majority of scrambled-text complaints HR teams report when first building their PandaDoc template library. See how onboarding document structure connects to client onboarding automation blueprints for the broader context.

Fix 2: Audit Every Token and Merge Tag

Broken tokens are the second most common culprit. A token that references a field not present in the associated workspace — or one that was renamed after the template was built — renders as visible code in the final document.

What to do: Open the template editor and use PandaDoc’s built-in variable panel to verify every token. Confirm each {{token_name}} maps to an active field in your workspace. Look specifically for:

• Tokens using underscores vs. spaces inconsistently (e.g., {{first_name}} vs. {{firstname}})
• Tokens referencing deleted custom fields
• Tokens duplicated with slightly different capitalization
• Conditional block tokens that reference logic no longer active

Remap any broken tokens to the correct field. If the field no longer exists, either recreate it in workspace settings or remove the token from the template.

Fix 3: Delete and Rebuild Corrupted Content Blocks

PandaDoc uses a block-based editor. Individual blocks — text, image, table, signature — can become corrupted, particularly after repeated copy-paste operations or partial saves during a session that timed out.

What to do: Identify which specific block is scrambled by clicking into each one individually. Once you locate the corrupted block, do not try to fix it in place. Delete the entire block, add a new block of the same type, and re-enter the content using clean plain text (see Fix 1 above).

Attempting to repair a corrupted block by selecting and reformatting text inside it rarely works because the corruption is typically in the block’s underlying structure, not the visible text. Deletion and rebuild takes three minutes and resolves the issue permanently.

Fix 4: Rebuild Problem Templates From Scratch

If the same formatting problem appears across every document generated from a specific template, the template structure itself is corrupted — not the individual documents. Patching individual documents wastes time without addressing the source.

What to do: Create a new blank template. Rebuild section by section using plain-text paste for all content. Re-establish your token mappings from the variable panel rather than copying them from the broken template. Test with a sample recipient before publishing.

This is also the right moment to standardize your template library. Teams that maintain more than a handful of templates without a naming and versioning convention accumulate structural debt fast. The 11 Onboarding Documents to Automate With PandaDoc First framework gives a practical starting point for deciding which templates to prioritize rebuilding.

Fix 5: Clear Browser Cache and Test in a Second Browser

PandaDoc is a browser-based application. Cache conflicts cause rendering problems that look like document formatting errors but are actually display artifacts local to your machine.

What to do: Before assuming a document is broken, perform a hard refresh (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac). If the problem persists, open the same document in a different browser. If it displays correctly there, the issue is a local cache problem, not a template problem.

Clear your browser cache fully, reload PandaDoc, and recheck the document. This resolves a meaningful percentage of reported formatting issues without any template changes required.

Fix 6: Fix PDF Export Layout Separately From Editor View

A document that looks correct in the PandaDoc editor can export to PDF with jumbled layout. This is a separate problem from editor-view formatting errors. It stems from block widths not aligning properly with PandaDoc’s PDF rendering engine.

What to do: Review each content block’s width setting in the editor. Blocks set to percentage widths that sum to more than 100% in a row layout will stack incorrectly in PDF output even when they appear side-by-side in the editor. Adjust widths, then use PandaDoc’s PDF preview (not the live editor) to verify the export before sending.

For documents with table-heavy content — compensation summaries, benefits breakdowns — always validate the PDF preview after any table column adjustment.

Fix 7: Use PandaDoc’s Version History to Restore a Clean State

If a template was working correctly and then broke after edits, PandaDoc’s version history is the fastest path to resolution. You do not need to rebuild from scratch if a clean version exists.

What to do: Open the template, navigate to the document menu, and select Version History. Locate the last version that displayed correctly, restore it, and verify the fix before making any further edits. Once restored, document what change caused the problem so you can avoid repeating it.

This fix is only available if the document was not permanently deleted or if the version history limit has not been exceeded in your PandaDoc plan tier.

Fix 8: Standardize How Your Team Creates and Edits Templates

Most recurring formatting problems are process failures, not software failures. When multiple team members edit the same template without a shared standard, conflicting formatting conventions accumulate until the document breaks.

What to do: Establish and document three rules for your team:

1. Always paste as plain text (never Ctrl+V directly from Word or Google Docs)
2. Never edit a published template directly — duplicate it first, edit the copy, test, then replace
3. Document every token used in a template in a shared reference so anyone editing it knows which fields must exist in the workspace

These three rules, applied consistently, prevent the majority of formatting incidents. Teams using PandaDoc at scale — particularly HR teams generating offer letters, onboarding packets, and contractor agreements in volume — see a dramatic reduction in formatting tickets once these standards are in place. For teams building this kind of process discipline, 7 Onboarding Bottlenecks PandaDoc Automation Eliminates shows where PandaDoc fits in the broader workflow.

Fix 9: Integrate PandaDoc With Your Workflow Automation to Eliminate Manual Data Entry

Many token errors and broken field mappings happen because someone manually typed data into PandaDoc fields that should have been populated automatically. Manual entry introduces typos, inconsistent field naming, and mismatched data that all appear as jumbled or incorrect content in the final document.

What to do: Connect PandaDoc to your HRIS, CRM, or ATS using Make.com so fields are populated programmatically from a verified data source. When a new hire record is created in your HRIS, a Make.com scenario pushes the correct field values directly into the PandaDoc token fields before the document is generated. No manual entry. No typos. No broken tokens.

This is the long-term fix. Document automation that relies on manual data entry will always produce formatting and accuracy errors at the rate humans make errors. Automation removes that variable entirely. The AI document automation guide covers the broader case for connecting document generation to your operational data layer.

For teams already using Make.com or evaluating it, 10 Automations That Are Finally Easy to Build With Make + AI includes document workflow examples that connect directly to this use case.

How to Know the Fix Worked

After applying any of the fixes above, verify success with these checks:

• Send a test document to yourself as a recipient (not just preview mode) — some formatting issues only appear in recipient view
• Export to PDF and review every page — PDF rendering is separate from editor view
• Generate the document from the actual trigger (form submission, HRIS record, manual send) rather than from the template editor alone
• Have a second team member review the output on a different device and browser
• Check that all tokens resolve to real values, not placeholder text or empty fields

If the same problem reappears within two document cycles, the root cause has not been fully addressed. Use the table at the top of this post to rediagnose.

Common Mistakes That Make Jumbled Content Worse

• Reformatting inside a corrupted block: Selecting all text in a broken block and applying new formatting does not remove underlying structural corruption. Delete and rebuild.
• Copying a broken template to create a new one: If the source template is corrupted, the copy inherits the corruption. Always start from a blank template when rebuilding.
• Testing only in editor preview: Editor preview and recipient view render differently. Always test in recipient view before declaring a fix complete.
• Ignoring token warnings: PandaDoc flags unmapped tokens with visual indicators. Teams that dismiss these warnings without fixing the underlying field mapping create documents that send with visible {{token}} text.
• Skipping the plain-text paste step for “just a small edit”: Small edits made with direct paste from Word are the most common source of new formatting problems in previously clean templates.

Frequently Asked Questions

Why does my PandaDoc document look fine in the editor but wrong when sent?

Editor preview and recipient view use different rendering paths. The editor shows your working view; recipient view renders the document as the signer sees it, which includes token resolution and PDF-layer formatting. Always test in recipient view before sending.

Can I fix formatting on a document that has already been sent?

You cannot edit a document that is already in the signing workflow without voiding it. Correct the template, then re-send a new document. For documents already signed, the formatting issue is a record concern only — contact PandaDoc support if the signed record needs annotation.

Why do my tokens show as visible code in the final document?

A visible {{token_name}} in the final document means the token is not mapped to an active field in your workspace. Open the variable panel in the template editor, find the unmapped token, and connect it to the correct field — or remove it if the field no longer exists.

How do I prevent formatting problems from recurring?

Three controls eliminate most recurring issues: plain-text paste as a team standard, a duplicate-before-edit policy for published templates, and a shared token reference document. Teams that add Make.com automation to populate fields programmatically remove the manual-entry error vector entirely.

Is jumbled content a PandaDoc bug or a user error?

The majority of jumbled-content cases are user-side formatting issues — primarily external formatting imported via paste, and broken token mappings. Genuine PandaDoc platform bugs are rare and are typically resolved in the same browser session after a cache clear. If the problem persists across browsers and devices after applying all fixes above, contact PandaDoc support with a specific document ID.

Additional Reading

• 9 PandaDoc Templates Every HR Team Needs for New Hire Onboarding
• 11 Onboarding Documents to Automate With PandaDoc First
• 7 Onboarding Bottlenecks PandaDoc Automation Eliminates
• Client Onboarding Automation: The 6-Step Blueprint
• Reclaim Your Day: How AI Document Automation Fuels B2B Growth
• 10 Automations That Are Finally Easy to Build With Make + AI — No Developer Needed
• How Sarah Compressed a 45-Minute Onboarding Process to Under 4 Minutes
• How to Run an OpsMap Audit Before Automating Anything
• Manual Data Entry: The Silent Killer of Business Productivity & Profit
• Drowning in Admin: How Solo and Small HR Teams Can Fix Broken HR Operations Without Burning Out