Fujifilm Business Innovation is the former Fuji Xerox, and its product names changed from DocuPrint and DocuCentre to Apeos and Revoria. The rename matters for drivers because support pages, manuals and model badges may still use the legacy name. Updating printer drivers Fujifilm devices begins with identifying the current model family and the controller underneath, not just searching for the name printed on the front panel.
Apeos office MFPs and Revoria production presses are different classes of equipment. Apeos devices use office drivers with finishing, authentication and scan features. Revoria production systems may use a Fiery or Fujifilm controller with its own driver, colour profile and workflow. Do not install an Apeos office package on a Revoria press because the badge and the print engine look related. Follow the controller documentation and test with production stock.
Need the general process first? Read the complete guide to updating printer drivers, including the five-stage framework and platform checks.
01 Manufacturer context
Why updating printer drivers Fujifilm is different
Fujifilm publishes PCL and PostScript drivers, model-specific packages and macOS support for Apeos devices. The regional support portals may list a device under its legacy Fuji Xerox name or its current Apeos name, and the driver version can differ. Use the exact model and region, and check the release notes for the controller generation. For office fleets, standardise the driver version and document finishing and authentication settings.
Revoria Press and production-class devices often need the controller’s driver plus a colour workflow, stock catalogue and RIP configuration. Driver updates should be coordinated with the production team and tested on a calibration job. On Apeos MFPs, scan-to-email, address books and user authentication live on the device. A new client queue will not recreate them, so back up or document the configuration before a clean install.
Apeos · ApeosPort · ApeosPro · Revoria Press · Revoria · DocuPrint · DocuCentre
Apeos print drivers (PCL/PostScript), model-specific packages, macOS PKG, Fiery/controller packages
Windows 11 / 10 / Server · macOS 14+ · Linux via CUPS (selected)
02 Windows 11 & 10
Updating printer drivers Fujifilm on Windows
Use the model-specific Apeos driver for office devices and the controller-specific package for Revoria. Remove the old queue before changing driver families, reapply options and authentication, then test print and scan. Check whether the support page uses the legacy Fuji Xerox name.
-
01
Record the baseline and clear the old queue
Note the exact model code, port, current driver version and any custom defaults. Remove the affected queue and, where relevant, its dedicated port. Restart before installing. This prevents Windows from silently reusing the stale driver.
-
02
Download the matching package from Fujifilm
Select the exact model, Windows version and architecture. Verify the digital signature and release notes. If you need scan, fax, finishing or accounting features, confirm that the package includes those components rather than assuming they are bundled.
-
03
Install deliberately, not by automatic discovery
Run the signed installer and add the printer on the intended port. For a network device, use a fixed address or DHCP reservation. If a generic queue already exists, remove it before adding the new one so the driver choice is unambiguous.
-
04
Reapply options and test real output
Reselect installed trays, finishers, colour profiles and authentication settings. Print from two applications, test duplex and colour, then reboot and print again. If scanning is part of the workflow, test it separately.
03 macOS 14 and later
Updating printer drivers Fujifilm on macOS
Install the current Fujifilm macOS package for Apeos models. AirPrint may provide basic printing. Revoria production systems require the controller’s macOS driver and colour workflow. Confirm Apple silicon support before relying on an older package.
-
01
Remove the existing queue before downloading
Open System Settings → Printers & Scanners and remove the device. This clears stale driver references and prevents macOS from quietly reusing a generic PostScript queue. Note any presets or custom paper sizes first.
-
02
Choose AirPrint or the vendor package on purpose
If basic printing is enough, readding the device as an AirPrint queue is the most maintainable path. If you need scanning, specialty media, colour profiles or finishing, install the current Fujifilm package and select the vendor driver explicitly.
-
03
Verify scan support outside the print dialog
Open Image Capture or the manufacturer’s scan utility and confirm the scanner is visible. A print queue can be healthy while scanning is absent. If the scanner is missing, fix discovery or the scan component before changing the print driver again.
-
04
Test, then record the working configuration
Print a real document, a colour page and a duplex job where supported. Note the queue protocol, driver version and macOS release. macOS updates occasionally replace a vendor queue with a generic one, so the record is your baseline.
04 Linux & CUPS
Updating printer drivers Fujifilm on Linux
Selected Apeos devices may work with CUPS using PCL or PostScript. Production controllers usually require the vendor’s supported workflow. Validate colour and finishing before using Linux in a production path.
Start with discovery, not a download
Check whether the device advertises IPP Everywhere or AirPrint before installing a vendor package. A driverless queue is often more maintainable, even if it exposes fewer specialty settings.
Validate the queue and the job
After adding or updating the queue, print a real document and check duplex, media size and colour. For label or POS devices, confirm the command language and calibration separately.
Linux support is model-dependent. Where the manufacturer does not publish a current package, a driverless queue or a validated generic PCL/PostScript driver may be the only supported option. Treat unsupported features as unavailable rather than “almost working.”
05 Field notes
Fujifilm driver traps to avoid
The three patterns below account for a disproportionate share of Fujifilm driver support cases. They are worth checking before you download another package.
Legacy Fuji Xerox names still matter
A device may be listed as DocuCentre or DocuPrint on older pages and Apeos on current ones. Search both names using the exact model code. The newest driver may be published under the current Fujifilm branding.
Apeos and Revoria are not one driver family
Office Apeos devices and production Revoria presses use different controllers and workflows. A driver that matches the print engine visually may not expose the controller’s colour and finishing features. Use the controller-specific package.
Production updates need a calibration plan
A Revoria driver or RIP update can change colour output. Test with a calibration job and a representative stock before releasing the queue to production. Keep the previous package and profile available for rollback.
06 Coverage
Fujifilm models and series covered
This guide applies to the Fujifilm families below. Model suffixes and regional variants matter, so use the label on the device or the configuration page before choosing a package.
The list is illustrative, not exhaustive. A driver page may cover additional models or exclude older regional variants. Always compare the exact model and release notes before installing.
07 Questions
Updating printer drivers Fujifilm: FAQs
01 Where are Fujifilm printer drivers now that Fuji Xerox is renamed?
Use Fujifilm Business Innovation’s support portal and search the current Apeos or Revoria model. If the device is older, search its former Fuji Xerox name as well. Match the region and controller generation before downloading.
02 Can I use an Apeos driver with a Revoria press?
No, unless the specific configuration is documented as compatible. Revoria production systems typically use a Fiery or Fujifilm controller with its own driver and colour workflow. Installing an office driver can produce incomplete or incorrect output.
03 Why did my Fujifilm scan workflow stop after a driver update?
The scan driver or device-side scan settings may be missing or reset. Apeos scan destinations and address books live on the device, while desktop scanning needs the scan component. Install the matching component, confirm discovery and test from the vendor utility.
08 Source of record
Official Fujifilm driver sources
This site does not host or mirror driver installers. Use the manufacturer’s support portal and verify the package before installation.
Manufacturer portals can change without notice. If a link no longer resolves, navigate from the manufacturer’s main support site and search the exact model. Brand names and trademarks belong to their respective owners.