TRY A KNOWN INPUT
Sample files. Checkable results.
Use these small, synthetic documents to learn a workflow before choosing a personal file. They contain no customer documents or real personal details. Each example states what to verify, not just which button to click.
1. Correct an invoice amount without rasterizing
Download the two-page original PDF and open Edit PDF Text. On page 1, select Invoice total: 100 USD
, replace it with Invoice total: 200 USD
, apply the edit, then prepare and download a separate copy.
Expected result: the PDF still has two pages. The new amount can be searched and copied; the selected original amount is gone. Keep this searchable reference.
and the second landscape page stay unchanged. Check spacing because longer text does not automatically reflow.
Inspect the reference edited output · Understand font and editing limits
2. Fill a form, then make a static copy
Download the one-page interactive form. It has a text field named customer with Sample Customer
, a checked approved checkbox and a status dropdown set to Ready
. In Sign & Fill PDF, change the text and checkbox, save and reopen the result to check the actual saved values.
For a static submission, open the original sample in Flatten PDF and export it. Expected result: the answers remain visible, but no interactive form widgets remain. Keep the interactive original for future changes. A static copy is not encrypted or tamper-proof.
Inspect the reference flattened output · Read the form checklist
3. Extract text and compare versions
Choose the original two-page invoice in PDF to Text and extract all pages with page separators off. Look for the original amount, reference line and Landscape second page
. Text order can differ in complex documents; this simple sample has one column.
View the expected text. Next, compare the original and edited invoice in Compare PDFs. Expect one changed page out of two and a replacement of 100 by 200 on page 1. Inspect the overlay as well; a text report alone does not prove visual equality.
What the reference outputs prove
These reference files are generated by the same PDF text-editing and flattening engine used by the tools, then reopened to check page counts, text runs and field structure. They illustrate a controlled case, not every font, damaged file or viewer. The generator is deterministic and the sample manifest records file hashes and expected properties.
Outputs are examples, not a substitute for running the browser tool on your own sample. Review the downloaded result in your receiving app. See how we test and what remains outside that scope.