PDF Form Calculations Not Working in Chrome, Preview, or Mobile?

When a PDF total does not update, the failure can come from two different places. The formula may be invalid, the source field may be blank, the dependency order may be wrong, or the value may contain a number format the calculation does not expect. But it can also be a viewer problem: the same file may behave differently in Acrobat, a browser PDF viewer, a mobile preview, or an email attachment preview.

That distinction matters because the fix is different. Formula and data problems should be fixed in the template. Viewer problems should change the output strategy. If the document is a final record, the most reliable answer is usually a flat PDF that already contains the computed value.

PDF calculation fields often depend on AcroForm JavaScript and calculation order. Adobe documents both the calculation setup and the order controls because dependent fields need a predictable sequence.¹ Browser and mobile viewers may display the PDF correctly while supporting only part of that live form behavior.

That is why DullyPDF does not treat live viewer recalculation as the final source of truth. Editable exports can include generated Acrobat-compatible actions, but DullyPDF also writes the precomputed current value into the output so the document opens with the expected result even when the viewer does not rerun every calculation.

Start with the source inputs. Confirm the number fields contain valid numeric values, not labels, currency text, commas, or blanks that the formula model does not expect. Then check whether the calculated output is actually read-only and whether all dependencies are still present after rename, mapping, or template edits.

Next, test the same PDF in Acrobat Reader and in the viewer where the problem appeared. If Acrobat updates the field but the browser does not, the formula is likely viable and the output strategy should change. If Acrobat fails too, the template calculation needs to be rebuilt or the dependency order needs review.

• Check source number inputs first.
• Check formula dependencies and missing fields.
• Check calculation order for chained totals.
• Compare Acrobat Reader against the target browser or mobile viewer.
• Export flat when the recipient does not need to keep editing live fields.

DullyPDF computes calculated outputs during materialization. That means the value is produced before editable download, flat download, Fill By Link response download, API Fill output, and signing source freeze. The PDF viewer can still provide live recalculation in compatible editable workflows, but the generated document does not start from an empty or stale calculated field.

This approach is especially important for external recipients. A customer, patient, applicant, signer, or accounting contact may open the PDF in whatever viewer their device chooses. A flat PDF keeps the completed value stable because the value is part of the page content rather than a script-dependent widget.

If the PDF came from a third-party tool with custom calculation JavaScript, DullyPDF does not trust or expose that script as editable source. The safer path is to rebuild the calculation through the DullyPDF formula model. That gives the template a known dependency graph, known source fields, and known output behavior.

Rebuilding is worth it when the form will be reused. It is not just a one-time repair. It turns a fragile viewer-specific calculation into a template rule that can be reused by Search & Fill, Fill By Link, API Fill, and signing workflows.