Skip to content
  • There are no suggestions because the search field is empty.

Working with Redacted, Watermarked, and Password-Protected Documents

A file was rejected during processing, and you're trying to figure out whether redactions, watermarks, or password protection are the problem.

The product does not detect password protection specifically

When a password-protected file fails to upload or process, the error message will not tell you that a password is the issue. The most common customer-facing error is File failed to upload, which is a browser-level default when the direct-to-storage upload fails — not a Valid8-authored message identifying the specific cause. If a password-protected file makes it past upload and is rejected during extraction, the rejection text tends to be generic (for example, a message about the document type not being supported) rather than naming encryption or password protection as the problem.

This means you need to check for these three things yourself:

  • Is the file encrypted or password-protected? Try opening it in a PDF reader outside Valid8. If you're prompted for a password, that's the issue — password-protected files are not supported on any upload path.
  • Was the file heavily redacted? Redaction removes text and images from the document permanently. If too much of the statement is redacted, extraction may fail because the system can't find enough structure to work with.
  • Does the file contain watermarks or stamps? Light watermarks (like a "COPY" stamp in the background) usually don't cause problems, but heavy overlays or annotations that obscure account numbers, dates, or transaction tables can interfere with extraction.
What to do

If your file is password-protected, you'll need to remove the password before uploading. Most PDF tools offer a "remove security" or "save as unencrypted" option if you have the password. Once the file is unprotected, try uploading again.

If the file is heavily redacted, and you're seeing rejections or incomplete extraction, you have two options: either provide a less-redacted version if one exists, or contact support with the engagement name and file details so they can help determine whether the file can be processed as-is.

For watermarks and stamps, the system typically handles light overlays without issue. If you're seeing rejections on a watermarked file, the watermark itself is probably not the cause — check whether the document type, account type, or date range might be triggering the rejection instead. See File Processing Stages and What Each Status Means for how to check what specific rejection text appears.