Stirling PDF: deleted text returns in the exported file

The editor shows an incorrect text item removed and a replacement in its place. After download or printing, the old text reappears underneath. An archived Stirling report describes this overlap in an edited document but does not name a precise build. Q1 The editor's correct-looking view is therefore not sufficient acceptance of the file you will send.

Identify the operation that was used

Editing existing text, adding a new text object and placing an annotation are different operations. Stirling documents them separately. Q2 Record which tool was actually used. A white rectangle placed over text may look like removal while doing something quite different to the underlying content.

Inspect the actual output file

1. Preserve and distinguish versions. Keep the source unchanged and give the export an unambiguous name. Confirm that the browser opens the new download rather than an earlier file with a similar name.
2. View it independently. Open the output in a second PDF viewer and compare both the affected area and print preview. An overlap shown by only one application differs from old text appearing consistently across viewers.
3. Check the text contents. Search for the old phrase and, where possible, copy text from the area. A match can demonstrate that information remains. Failure to find a phrase alone does not prove complete removal from a scan or image.
4. Minimise the editing sequence. Reproduce on a harmless copy with one affected location. Record the tool, apply/save step and download sequence. This helps distinguish an unapplied preview change from incorrectly generated output.
5. Clarify the purpose. For a content correction, producing a clean export from the originating software is often easier to audit. For permanent removal of confidential information, use the dedicated redaction operation and verify its saved output. Q3

Establish a dependable final version

Send only the verified file. For invoices and other business documents, make the substantive correction through the responsible source process; a PDF overlay can create inconsistent versions. For signed documents, also inspect signature status after editing rather than assuming the previous validation result still applies.

For handoff, prepare the software version, exact tool sequence and a minimal example without customer data. Before-and-after images help describe the symptom but do not replace inspection of the saved content. Keep the source and output distinguishable so that testing does not accidentally validate the wrong file.

Frequently asked questions

Is covering text the same as deleting it?

No. Establish what the chosen operation does and whether the original information remains in the output.

Should I export everything as an image?

That changes searchability, quality and other properties. It may fit a deliberate workflow, but it is not a general repair for every editing failure.

Describe your case