More

Troubleshooting

Scanner discovery problems, scan and feeder errors, and recovering your work.

No scanners found

If the device picker says No scanners found, work through this list — it resolves nearly every discovery problem:

  1. Wake the scanner. Many scanners disable their network interface in deep sleep. Wake it from its own panel, then tap Refresh scanners in Neo.

  2. Same network? Your iPhone/iPad and the scanner must be on the same local network. Watch out for separate guest Wi‑Fi, a 2.4/5 GHz split with client isolation, or VPN profiles that block local traffic.

  3. Local Network permission. In the iOS Settings app, open Privacy & SecurityLocal Network and make sure PDFScanner Neo is allowed. Without it, discovery finds nothing — Neo will only offer the camera.

  4. Does the scanner speak AirScan/eSCL? Neo uses the driverless AirScan/eSCL standard — most network scanners from the last decade support it. If another AirScan app (or a Mac’s driverless scanning) can’t see the scanner either, the scanner itself is the issue; check for a firmware update or an “AirPrint/AirScan” setting on the device. USB-only scanners are not supported.

  5. Restart in this order: the scanner, then the app, then — if needed — the router.

Scan errors and what they mean

MessageWhat to do
The scanner could not be reached on the local network.Discovery worked earlier, but the connection now fails — usually sleep or a changed IP address. Wake the scanner and refresh.
The scanner did not respond in time…Check that it is awake and reachable, restart it if needed, then try again.
The scanner did not return a page within … seconds.The job stalled mid-scan. Check the scanner’s display, cancel any stalled job there, then try again.
The scanner is busy or unavailable.Someone (or something) else is using it — many scanners handle only one job at a time. Wait a moment and try again.
The scanner requires authentication.The scanner’s administrator has restricted scanning — check its admin settings.
The secure scanner connection failed.The scanner’s HTTPS endpoint misbehaves (self-signed or broken TLS is common on older firmware). A firmware update on the scanner is the sustainable fix; restarting the scanner sometimes helps too.
The scanner returned HTTP …An unexpected reply from the scanner’s firmware. Restart the scanner and try again; if one specific setting triggers it, try another resolution or source.

Document feeder (ADF) problems

Feeder errors come from the scanner’s own sensors, and the message says exactly what it detected:

MessageFix
The automatic document feeder is empty.Load paper and try again. With Source set to Automatic, Neo retries once on the flatbed instead.
Paper is jammed in the automatic document feeder.Clear the jam and try again.
The automatic document feeder hatch is open.Close it and try again.
…could not pick a sheet. / …picked multiple sheets.Fan the stack, straighten it, reload — worn feed rollers make this more frequent.
…input tray is overloaded.Remove some pages and scan in smaller batches.
The document is too long/short for duplex scanning.The feeder’s duplex path can’t handle this paper size — scan those pages one-sided, or use Fake Duplex.

Camera problems

Opening and importing files

Smart Save and Apple Intelligence

My work disappeared after a restart

That’s by design — Neo starts every launch with an empty workspace. Tap the clock icon (Open Previous) to restore the previous session, including page, zoom and scroll position. See The scan workspace.

A processed page looks wrong

Select the page and choose Revert to Scanned Original — it returns to the exact scanner output, undoing crop, conversion and deskew in one step. Then reprocess with different settings, e.g. the Alternative Black and White Conversion for colored originals. See Cleaning up pages.

Purchase and Pro issues

Still stuck?

Reach out through pdfscannerapp.com — include your scanner model and what the status line or alert said, and you’ll get a much faster answer.