ExtractFoxHow we test
By ExtractFox team · Updated
Examples are real runs
When a tool page shows an input and the data that came out of it, the output is what the live extractor returned for that input. We shorten long results and say so; we don't correct fields by hand. If a field came back wrong or empty, the example shows that too.
Sample documents
Inputs are documents we made for the purpose or published specimens, such as the ICAO specimen passport. They are never customer files: uploads are processed and deleted, so we couldn't use them even if we wanted to. Where a sample is useful to try yourself, the page links it for download.
What runs after every deploy
An end-to-end script runs against the production site: it signs up a test account, extracts a generated invoice and checks the total comes back exactly, decodes a QR code, pushes a large PDF through the upload path, opens a checkout without paying, and checks that a purchase grants credits. Separately, the site checks every few hours what share of recent extractions failed and alerts us when it rises.
What we don't claim
We don't publish an accuracy percentage, because a single number across invoices, passports and handwriting would mean nothing. Statements about other products on comparison pages link to that product's own pricing or documentation; anything we couldn't source was removed.
Dates
The date under a page's title is the last time its content changed, not the last time the site was rebuilt.