ScanSnap on Sierra - Your Experience?

ScanSnap on Sierra – Your Experience?

The latest Mac operating system, macOS 10.12 Sierra, is out on September 20. How does the Fujitsu ScanSnap work with it? Are there any ScanSnap Sierra issues?

Whenever a new Mac OS is released there are often a few bumps here and there, but this time there are some warnings from Fujitsu.

Update 10/06/2016: Fujitsu has released a fix for current-model ScanSnap scanners that fixes new PDF files being created on macOS Sierra.

Fujitsu Global has released a somewhat alarming compatibility notice. Here are some highlights:

>Problems regarding the compatibility with macOS Sierra have been found.
>Please do not use ScanSnap applications on macOS Sierra. Also, before upgrading your OS to macOS Sierra, please be sure to make a backup copy of the PDF files created by using ScanSnap applications.
>We will provide you the solution to these issues as soon as available.

That doesn’t sound good! From reading the notice, it seems some pages may become blank when scanning on Sierra.

I posted the notice on Twitter and received a number of messages saying that everything is working fine for them.

So it seems that some people have issues and others don’t. I am guessing that depends on how they’re scanning and what they’re scanning into.

Update 10/06/2016: Fujitsu has released a fix for ScanSnap Manager and CardMinder for the following models: iX500, iX100, SV600, S1300i, S1100i.

To download the fix, run Online Update by going to Help > Online Update after right-clicking on the ScanSnap Dock icon.

The fix for S1500, S1500M, S1300, and S1100 is expected by October 17th.

There is a “second category” of fixes that is still TBD. Here’s what they write:

Fujitsu is committed to providing our customers a great experience with their ScanSnap investment and we will continue to work diligently to provide a fix for older PDF content created by ScanSnap capable to be modified on macOS Sierra. Though the conditions whereby PDF content could be damaged is limited and specific, please continue to exercise best practices in digital retention for any reason by keeping a secure back-up of your important PDF files so that you may continue to transact with your data with the safety of having a copy.

So if you have older PDFs that are having issues that were were created after Sierra but before these fixes were applied, they’re still working on a fix.

Read this Fujitsu notice for more on the timeline and the fixes.

Fujitsu has also created a pretty comprehensive FAQ showing what exactly is impacted. As you can read in the September 27 update below, it is pretty limited.

Update 09/27/2016: Fujitsu has updated their ScanSnap Community alert with more specific functionality to avoid and a timeline for a fix.

Do not use [ScanSnap Organizer], [ScanSnap Merge Pages], or [CardMinder] Do not use Excellent mode when scanning A3 (11.7 in. x 16.5 in.) documents

No image data will be lost nor any blank pages produced when content that has been scanned in the A4 (8.3 in. x 11.7 in.), Letter (8.5 in. x 11 in.), Legal (8.5 in. x 14 in.), or smaller sizes is saved.
Do not select the following functions in either Quick Menu or Application

  • [Scan to Print]
  • [Scan to Evernote (Document)]
  • [Scan to Evernote (Note)]
  • [Scan to Google Drive]
  • [Photographs]

A fix for the above problems is expected to be made available in the middle of October, 2016.

I guess this explains why so many DocumentSnap readers are reporting no issues – it seems as if it’s a very limited set of circumstances that cause the issue. Read the entire Fujitsu article for more.

ScanSnap Sierra Compatibility

Based on the above, the current ScanSnap models are supported on Sierra:

  • iX500
  • iX100
  • SV600
  • S1300i
  • S1100i

Older models are not yet supported.

See the Fujitsu fix notice for manual instruction links if Online Update doesn’t work.

Your Experience?

Have you done the macOS Sierra upgrade? How is your ScanSnap and related software working?

I’d appreciate it if you left a comment either way. I’ll update this post as new information becomes available.

About the Author

Brooks Duncan helps individuals and small businesses go paperless. He's been an accountant, a software developer, a manager in a very large corporation, and has run DocumentSnap since 2008. You can find Brooks on Twitter at @documentsnap or @brooksduncan. Thanks for stopping by.

Leave a Reply 43 comments

Arthur P. Johnson - February 10, 2018 Reply

I’ve been trying to reinstall ScanSnap Manager and my i500 on a brand new iMac Pro running the latest edition of High Sierra (10.13.3) — for the past two hours. I cannot for the life of me get the ScanSnap Manager Icon to turn blue. The same software and scanner ran flawlessly on my Mac Pro (late 2013) with the same release of High Sierra.

Any suggestions? My next stop is Twitter…

THANKS in advance for your help!

    BRian - May 5, 2018 Reply

    I Have been using the scan snap s500M for ever and it is a powerhouse for processing. All of a sudden on High sierra I have been getting all the workings. I dug deeper – Fujitsu has stopped all support for my scanner and it blows my mind that a scanner that still works and is fast and costs over $500 is dicontinued. I’m going to try the trial version of Scan Tango to see if that allows it to still work for me. I do not have the same day to day need to use my scaner that I did ( altough I would like to ). I have had in the field work arounds getting documents into Evernote. Check on the Fujitsu site to see if you have the latest software and if your scanner is supported.

    Erik Beck - June 13, 2018 Reply

    I’m in the exact same boat. New imac, can’t connect no matter what I try. Did you ever find a solution?

Dietmar - September 26, 2017 Reply

Hi everybody,
it sounds incredible, but the Fujitsu Scansnap S300M does work on OS X 10.13 High Sierra! I was very angry because the scanner did not work under OS X 10.12 Sierra, as the Scansnap Manager won’t start anymore once Sierra was installed.

Now I upgraded to High Sierra and I was very surprised to learn that everything (!) works as before! Even the scan directly to Devonthink Pro Office and does work!

Fujitsu had discontinued the support for that scanner by OS X El Capitan, yet the last OS X version to be supported was Yosemite (10.10).

There are no plans to add support for future releases of OS X, so I am very glad to see that it just works fine on High Sierra.

The Scansnap Manager version I used for this test is 2.2 L 11 on OS X High Sierra 10.13., connected via USB 2.0 to my Macbook Pro 9,1 (Mid 2012, 15 inch). (This Macbook Pro has USB 3.0 on board, actually, but the Scanner does not and the cable does not either).

Give it a try!

Bill Eccles - May 29, 2017 Reply

It looks like Sierra 10.12.5 broke my installation of ScanSnap Manager. I’m running v3.2L91 and cannot find a setting of ScanSnap Manager which will successfully produce a file.

After successfully scanning (i.e., paper moves through) a page, the progress window shows 0 pages /0 sheets scanned, and that window disappears. Another window pops up with the error message “There is not enough memory.(0x00000009) Close other applications or delete unnecessary files to secure enough disk space and memory, and then try again. If the problem persists, restart the computer.”

Plenty of free space on the drive, no problem with permissions on the destination folder (that I can tell, anyway), and to the best of my knowledge, the only thing I’ve done is update to 10.12.5.

Anybody have similar experiences, or am I an outlier?

    Eric - July 14, 2017 Reply

    Scansnap v3.2L91, for OS Sierra 10.12.5 has also rendered my Scansnap s1300 DOA. Wonderful blinking blue light and no joy.

    Bill Eccles - July 14, 2017 Reply

    I ended up reinstalling Sierra and the scanner software works again. No clue why it stopped, so YMMV.

      MorganV - July 21, 2017 Reply

      For anyone using an S1500 on a mac, you can install the driver for the S1300i and it works!
      Just installed under Sierra 10.12.5. And by the way, many more features than the 3.2 software. This installer will install ScanSnap manager 6.3 L50

        Bill Eccles - August 2, 2017 Reply


        OK, so I installed it on a machine that didn’t have a problem, but it’s true that the S1300i software works with the S1500M. Yay! What a great discovery!

        Thank you!

        David Henry - January 14, 2020 Reply

        You are a legend

    MorganV - July 21, 2017 Reply

    I’m getting exactly the same problem since updating to 10.12.5. Scan snap S1500 running SS Manager 3.2 L80.

    Tried reinstalling ScanSnap manager, deleting all SS preferences but no luck. I’ll keep investigating…

sharon - March 30, 2017 Reply

Maybe someone here knows what the problem is, so going to take a chance and ask.. this is nothing to do with Sierra, because it did the same before Sierra. MacBook Pro/ and ix500. When connected with a USB it sometimes works, but more often than not, I get the flashing orange light. When connected (supposedly) via network, same thing happens. If I shut down, unplug, say lots of 4 letter words it then works wirelessly, but try to do the same 10 hours later, it’s the same malfunction. Anyone here know what’s going on? I have other wired older scan snaps so resort to using them, but this has to be fixed once and for all.

Richard Sears - March 1, 2017 Reply

I just tested my S500M with Sierra on a test drive (I couldn’t risk it on the main drive) and it scans fine.

Anjanette - January 24, 2017 Reply

Question: I have a ScanSnap s510M that’s worked well for years. I just barely upgraded to macOS Sierra and the Scansnap manager program won’t pull up to scan documents. Fujitsu says that they’re no longer offer support for the s510M. Any suggestions? I’d rather not have to but a new scanner if I don’t have to. Thanks!

Kurt S. - January 5, 2017 Reply

Using Scan-snap S300m with Paperless (by Mariner Software) crashes like crazy with Sierra OS. I am assuming this is because of Fujitsu’s not wanting to update any software for my trusty S300m. I have the latest version of Paperless, too. It was updated for Sierra. I dont want to buy another scanner since my is running just fine. Thoughts?

Ronald - December 28, 2016 Reply

They gave up ABBYY support for FUJITSU Image Scanner ScanSnap iX500 under Sierra? They say under Compatible Operating Systems, macOS Sierra v10.12 “ABBYY FineReader for ScanSnap™ 5.0” :
“Check with each vendor for compatibility information.” So they don’t even say anymore if its supported or not, like they did before! See
and then specifications.

Alex - December 19, 2016 Reply

Since updating to macOS 10.12.2 I have found that Preview destroys the OCR layer of PDFs scanned and OCR’d with the latest ScanSnap Manager software if you make any sort of edit with Preview (e.g. deleting or reordering pages). After editing and saving with Preview, the PDF is no longer searchable and text is not selectable. Managed to replicate the problem on another Mac running 10.12.2. Doesn’t seem to affect PDFs scanned and OCR’d with other scanners or applications. Just wanted to warn everyone to perhaps wait before updating, and check that they haven’t unwittingly destroyed their OCR if they have already updated.

    Jakub - December 20, 2016 Reply

    Hey Alex.

    I can confirm that behaviour. I found out yesterday by accident, while merging scanned OCR-PDF. Unfortunately this bug seems not to be addressed yet. I have tried to merge older scanned files, so I am not sure if this is due to the pre-Sierra scans.

      Alex - December 20, 2016 Reply

      Hi Jakub, thanks for the reply. It’s good to know I’m not the only one who has noticed this bug.

      I can confirm that this problem also affects new scans made in Sierra with the updated ScanSnap Manager software. My affected PDFs were scanned in both 10.12.1 and 10.12.2.

      I also tried scanning without OCR and then OCRing separately using ABBYY FineReader for ScanSnap and those PDFs also had their OCR layer destroyed after editing with Preview. A PDF scanned and OCR’d with Office Lens for iPhone was unaffected when I tested that.

    Brooks Duncan - December 20, 2016 Reply

    Thanks for this – just wrote a post about it!

Chris Gleason - November 20, 2016 Reply

I didn’t even realize that my S300M was not supported anymore until I looked at the Fujitsu site and saw this:

“ScanSnap S300M does not support macOS Sierra. There are no plans for adding support in the future since the support for ScanSnap S300M has already ended.”

So I’m basically prevented from moving to Sierra until I buy a new scanner? When my S300M finally does break down, you can be sure I won’t be buying a Fujitsu…

Jennifer - October 27, 2016 Reply

Waited to download Sierra until the update from Fujitsu update was ready, my iX500 works great, no problems.

    Cal - October 29, 2016 Reply

    So Jennifer, you took Sierra’s latest version and did the scansnap patch?

tom miller - October 26, 2016 Reply

I upgraded to MacOS, then installed the latest update from Fujitsu. Haven’t had any issues at all. Thanks for letting us know about the original problems!

Barry Sullivan - October 25, 2016 Reply


Yesterday Apple released macOS Sierra 10.12.1 and in the release notes one of the updates is:

“Improves compatibility with Fujitsu’s ScanSnap scanning software”

It looks as if both sides had work to do in resolving the issue.

    Brooks Duncan - October 25, 2016 Reply

    Thanks for the heads up, Barry!

Ed - October 15, 2016 Reply


I upgraded to Sierra a couple of days ago and my ScanSnap S1300i (using ScanSnap Manager Version 6.3 L60 seems to work fine. I have ScanSnap opening the PDF files in PDF Expert 2.0. I have also scanned photos into the Photo’s app with no issues.

Alexis Doval - October 13, 2016 Reply

ScanSnap Receipt has display issues on Sierra. Cells with drop down menus don’t show content. Any fix in sight?

fotofah - October 12, 2016 Reply

I’m running Sierra with my ScanSnap i11300, running ScanSnap Manager v3.2.71 without any problems (as far as I can tell). But thanks for this post!

Dave Price - October 9, 2016 Reply

I upgraded to Sierra a couple of days ago and my old ‘unsupported’ ScanSnap S510M seems to work fine. I created a few PDF files which survived editing in PDFPenPro 7. Am using ScanSnap Manager Version 3.2 L71.

Patrick Gallagher - September 30, 2016 Reply

No problems with a S1500 using Scan to Evernote.

DaveSouthwick - September 29, 2016 Reply

I use Accountedge and PDFPenPro and I am having issues. If I scan a document with ScanSnap into PDFPenPro. it displays fine. But when trying to attach a PDF to an invoice or other document in AccountEdge, AccountEdge will not recognize it. And if i force OCR in PDFPenPro, I will get a blank PDF except for the Stamps such as “Paid” or “Copy” that I can add to the PDF as I wish.

Paul Sture - September 28, 2016 Reply

There are further details in the link “Details on specific conditions” at the bottom of that Fujitsu page

Fortunately I only scan A4 or less and use Folder output, so it looks like I’m OK with my S1300i.

Nigel - September 28, 2016 Reply

No problem using an old s300m , using the older scansnap software and scanning to desktop, OCRing with PDFPen Pro.

    Lucy - October 17, 2016 Reply

    Hi Nigel,
    Can you tell me what older scansnap software you are using (for which OS – Lion, Maverick, etc) because I can’t get my S300M to work and I really don’t want to buy another scanner when this one works just fine.


Wayne - September 22, 2016 Reply

Currently using my iX500 Scansnap with macOS Sierra and Devonthink Pro Office…. Everything appears to be working perfectly

David Givnish - September 21, 2016 Reply

I’ve been scanning through ScanSnap Quick Menu for a couple of weeks without this problem . Workflow is either “Scan to Folder” or “Scan to DevonThink Pro”. No blank pages and the OCR appears to be working correctly.

Bernd Traber - September 21, 2016 Reply

As before with Mavericks and El Capitan I managed to get my old 510M to work. I downloaded ScanSnap_V22L11.dmg and then ScanSnap_V22L16.dmg. Ran both installers. I then dropped Finereader I got from an old install and dropped it into the programs folder.

Tweaked and set my preferences in both finereader and Fujitsu Scan Snap Manager.

And I scanned successfully to my specific file folder. Apparently it can be done.

Tim Stringer - September 19, 2016 Reply

Thanks for the post, Brooks.

I spoke to someone in Fujitsu’s tech support team earlier today. He confirmed that there is a compatibility issue that impacts macOS Sierra and it sounds like their engineering team are working on a fix. He wasn’t able to provide even an approximate ETA for the fix.

I wasn’t able to get much more information on the issue. He mentioned something about image data being lost if an OCR’d PDF is edited in any way (at least that’s what I understood). It’s not clear if there are issues if the OCR feature is turn off. He advised me to keep any paper I scan if I use the ScanSnap software under macOS Sierra…just to be on the safe side.

In the short-term, my plan is to scan to my iPhone or iPad and then to transfer the files to my Mac via Dropbox. It’s not ideal, but it will do the job until Fujitsu addresses this issue.

Mike Harahan - September 19, 2016 Reply

Can report same as Karen. Problem occurs when reading pdf scans with Apple’s Preview. Have no probs with other pdf viewers.

I don’t think the problem has to do with ABBY’s engine. I have run scans with their ISIS software without experiencing the blank page syndrome.

That said, I am not upgrading my work machine until I get word from Fujitsu that they have an upgrade that is Sierra compatible.

Karen - September 19, 2016 Reply

I’ve been using ScanSnap quite happily under the various betas of macOS Sierra. I did have one document which created a blank page when viewed within Preview (and crashed macOS), but it displayed OK with other PDF viewers so seems to be as much a Preview bug as a ScanSnap one.

    Brooks Duncan - September 19, 2016 Reply

    Interesting re: other applications. Thanks Karen! I wonder if it is something to do with ScanSnap Manager or with ABBYY’s OCR.

Leave a Reply: