Product updates

Changelog

What's new on PDFly — product updates, tool improvements, and fixes as we ship them.

September 2026

Troubleshooting sections added across the tool library

We audited every production PDF tool for Troubleshooting coverage, then wrote tool-specific sections for the tools that were missing one — each based on the tool's actual code and behavior, not generic filler.

  • Added dedicated Troubleshooting sections to 47 tool pages across three rollout batches — high-priority tools (merge, split, sign, unlock, OCR, AI tools, redact, fill forms), conversion tools, and the remaining editing/utility tools.
  • Each section covers the real error messages, limits, and edge cases a tool actually produces — verified directly against its code — with links to the right companion tool (e.g. Unlock PDF or Repair PDF) where relevant.
  • 9 tools already had strong, tool-specific Troubleshooting sections and were left untouched; no existing HTML, styling, or functionality was modified anywhere in this pass.

All 56 tool pages on PDFly now have consistent, accurate Troubleshooting guidance.

Known issues found during this audit

Writing accurate Troubleshooting copy meant testing each tool's actual behavior. Two functional issues turned up that documentation alone can't fix — they're logged here for transparency and are being tracked for a code fix:

  • Image Compressor: the quality slider currently doesn't reduce output file size — compressed downloads can come back close to the original size.
  • Metadata Editor: saving can fail with "Failed to update metadata" whenever the Keywords field contains text.

August 2026

SEO & trust foundation

A round of site hygiene and trust-signal work to strengthen PDFly's foundation ahead of further product work.

  • Closed an exposed .git directory on the production site.
  • Published a dedicated Cookie Policy.
  • Implemented a cookie consent banner with a working "Manage Preferences" flow, tested end-to-end.
  • Gated Google Analytics and Ahrefs tracking behind explicit user consent.
  • Excluded backup folders from deployment via .vercelignore.
  • Updated and resubmitted the sitemap.