Papaya PDFText editing gets weird when the PDF does not actually contain a full usable copy of the font. That happens constantly.
The font you see may not be available
Many PDFs include only the font pieces needed to draw the existing page. Other PDFs rely on fonts that are licensed, proprietary, or only available on a specific platform. The page looks right, but a PDF editor may not be allowed or able to use that exact font for new text.
That is why editing one word can be harder than it looks. Matching the original appearance is not just about picking a font name. The editor has to make the new text feel like it belongs in the document without breaking the rest of the page.
How Papaya PDF handles it
Papaya PDF first tries to preserve the font details already present in the file. When the PDF gives us enough usable information, that keeps edits visually close to the source.
When the original font cannot be used, Papaya PDF uses its custom engine to choose a close available replacement. The goal is simple: keep the edit looking like it belongs on the page, even when the original font is incomplete, unavailable, or constrained by licensing and platform limits.
This is only possible because Papaya PDF controls its own PDF engine. Instead of relying on a generic browser font swap, the engine can make font decisions as part of the same editing and export pipeline. That gives Papaya PDF a better shot at preserving the look of the document and saving a PDF that renders correctly in other viewers too.
This is one of the places where Papaya PDF is doing real PDF work, not just drawing text over a screenshot. The custom engine is what makes serious PDF editing feel natural.