How to Run CADLink Digital Factory V12 DTF on Mac M4 with Parallels & Windows 11 ARM

By Familia Fabrica · Workshop tested: 9 September 2026

Yes. CADLink (Fiery) Digital Factory V12 DTF can run on an Apple Silicon Mac using Windows 11 ARM through Parallels Desktop — in our tested M4 setup.

At Familia Fabrica, we successfully migrated our licensed Digital Factory V12 Direct To Film Edition workflow from an Intel Windows laptop to a MacBook Air M4 running Windows 11 Pro ARM through Parallels Desktop 27.0.1.

Digital Factory initially launched, but importing artwork produced a PostScript Conversion Error. After correcting that, RIP processing reported a Missing ICC file error. We eventually traced both problems to the application's saved folder paths.

The solution in our case was surprisingly simple: preserve the complete original Digital Factory folder and its original Windows path.

After restoring the original folder structure, Digital Factory could:

• launch successfully;

• import PNG artwork;

• process artwork through the RIP;

• access the required ICC profiles;

• use our existing DTF printer queue; and

• send and physically print DTF jobs through our Epson ET-8550 DTF setup.

We did not have to reconnect the printer, reassign it in Digital Factory Queue Manager or create a new queue. The same physical printer was already accessible from both our original Windows laptop and Windows 11 running through Parallels on the Mac. Once the Digital Factory paths were restored, sending RIP/Print through the existing queue resulted in normal physical printing.

This article documents the actual setup, folder paths, errors, repair and successful print workflow we used, rather than assuming that an application launching under Windows ARM means the complete DTF workflow works.

Quick answer: In our installation, the working application had to remain at C:\Digital Factory v12 Direct To Film Edition\. Copying the complete folder to that same location inside Windows 11 on Parallels restored the paths expected by Digital Factory. Because our printer was already installed and accessible from Windows in Parallels, the existing Digital Factory queue worked without reconfiguration and successfully sent the DTF job to the printer.

Tested by Familia Fabrica

This is a real production workflow, not just a compatibility test

Digital Factory is part of the DTF workflow we use at Familia Fabrica for large-format graphic apparel produced through our workshop.

Examples of artwork handled through this workflow can be seen in our DC Comics collection, Marvel Comics collection and 90s Nostalgic collection.

Large graphic pieces such as our Batman Knightfall — Bane Breaks Batman T-Shirt, Vintage Superboy-Prime vs. Batman Who Laughs T-Shirt, Hulk Smacking Ant-Man Avengers T-Shirt and Emperor Victor von Doom Doomquest T-Shirt illustrate the type of detailed artwork for which we use DTF production.

That distinction matters because our result is not based only on getting PSQueue.exe to open. We verified artwork import, RIP processing, the existing printer queue and physical DTF printing.

Important limitation: this documents our specific working configuration. It should not be interpreted as official Fiery support for Apple Silicon, Windows ARM, Parallels or every printer/driver combination.

Before you start: licensing and compatibility

For licensed users only — this is not a crack, activation bypass or licensing workaround.

This guide documents the migration of an existing licensed Windows installation of Digital Factory. It does not bypass activation, extend a trial, provide software or license files, or circumvent Windows ARM emulation.

You must hold your own valid Digital Factory license and follow Fiery's applicable installation, transfer and activation terms.

This is an independent Familia Fabrica workshop guide and is not endorsed by Fiery, CADLink, Microsoft, Apple or Parallels.

Apple Silicon also matters. Parallels runs Windows on ARM on M-series Macs, while Windows can emulate many Intel Windows applications. Windows drivers and other low-level components still need appropriate compatibility.

See Parallels' explanation of Windows 11 on ARM for the virtualization side of the setup.

The key fix: preserve the original Digital Factory installation path

The most important lesson from our migration is:

Do not assume that moving the Digital Factory folder to a different Windows directory is harmless.

Our working Windows installation used:

C:\Digital Factory v12 Direct To Film Edition\

During migration we initially copied it under:

C:\Program Files\

Digital Factory itself could still launch, which made the problem misleading.

However, parts of the existing configuration were still looking for resources under the original path.

For our installation, the expected executable was:

C:\Digital Factory v12 Direct To Film Edition\PSQueue.exe

and Digital Factory expected supporting resources underneath the same original folder tree.

Restoring that structure solved the migration problem.

Important: your original path may be different

C:\Digital Factory v12 Direct To Film Edition\ is the path used by our installation. It is not a universal requirement that every Digital Factory installation must be located directly under C:\.

Before copying anything, check the Target and Start in properties of the working Digital Factory shortcut on your original PC.

If your working installation uses another path, preserve your actual working path on the destination wherever possible.

How to migrate Digital Factory V12 to an M4 Mac with Parallels

Step 1 — Find the working Digital Factory folder on the original Windows PC

Close Digital Factory and finish any pending print jobs.

Open:

File Explorer → This PC → Local Disk (C:)

In our installation, the folder was:

C:\Digital Factory v12 Direct To Film Edition\

Inside it we confirmed the presence of:

PSQueue.exe
Helper\
Queues\
Rip\

If your installation is somewhere else, right-click the working Digital Factory shortcut and choose Properties.

Record:

Target
Start in

Do this before moving the software.

Step 2 — Copy the complete Digital Factory folder to a USB drive

Connect a USB drive with sufficient free space.

Our Digital Factory application folder was approximately 4 GB, so allow additional space for backups and other resources.

Copy the entire:

Digital Factory v12 Direct To Film Edition

folder.

Do not copy only:

PSQueue.exe

and do not copy only the Desktop shortcut.

For example, if Windows assigns the USB drive E:, the USB copy would look like:

E:\Digital Factory v12 Direct To Film Edition\

After copying, confirm that the USB version contains at least:

PSQueue.exe
Helper\
Queues\
Rip\

Keep the original Windows installation intact until the migration is completely verified.

If you have custom ICC profiles, printer resources or other files stored outside the Digital Factory folder, back those up separately and record their locations.

Step 3 — Connect the USB drive directly to Windows 11 in Parallels

Start the Windows 11 virtual machine on the Mac.

Connect the USB drive.

If Parallels asks whether the USB device should connect to Mac or Windows 11, choose:

Windows 11

If the drive does not appear, use:

Parallels → Devices → USB & Bluetooth

and connect the USB drive to the Windows virtual machine.

Parallels also documents USB device connection here:

How to connect USB devices to a Parallels virtual machine

Inside Windows, open:

File Explorer → This PC

and confirm that the USB drive is visible.

Step 4 — Copy the complete folder to the same Windows path

This was the critical step in our setup.

On the USB drive, copy:

Digital Factory v12 Direct To Film Edition

Then inside Windows running in Parallels, open:

This PC → Local Disk (C:)

and paste the folder there.

For our installation, the final structure was:

C:\Digital Factory v12 Direct To Film Edition\PSQueue.exe
C:\Digital Factory v12 Direct To Film Edition\Helper\
C:\Digital Factory v12 Direct To Film Edition\Queues\
C:\Digital Factory v12 Direct To Film Edition\Rip\
C:\Digital Factory v12 Direct To Film Edition\Rip\system\clinks\

Do not accidentally create an extra folder level

You want:

C:\Digital Factory v12 Direct To Film Edition\PSQueue.exe

not:

C:\Digital Factory v12 Direct To Film Edition\Digital Factory v12 Direct To Film Edition\PSQueue.exe

For our particular source installation, do not place it under Program Files, because that would no longer reproduce the original working path.

Again: if your original PC uses a different working path, reproduce that path instead.

Step 5 — Open PSQueue.exe and complete the supported activation process

Open:

C:\Digital Factory v12 Direct To Film Edition\PSQueue.exe

Use your own valid Digital Factory license and follow Fiery's applicable transfer or activation procedure.

Fiery provides information about its activation self-reset option for eligible situations.

Copying the application folder does not bypass activation and does not grant an additional license.

For our installation, the shortcut properties should point to:

Target:
"C:\Digital Factory v12 Direct To Film Edition\PSQueue.exe"

Start in:
"C:\Digital Factory v12 Direct To Film Edition"

Notice that Target contains PSQueue.exe, while Start in contains only the folder.

Make sure you launch the copy on the virtual Windows C: drive — not PSQueue.exe directly from the USB drive.

Step 6 — Test image import, RIP and physical printing

Do not immediately delete old files or start changing profiles.

First create or use a small PNG stored locally inside Windows.

Then:

1. Launch Digital Factory.

2. Import the PNG.

3. Verify that the artwork appears correctly.

4. Inspect its dimensions.

5. Trigger RIP processing.

6. Check whether an ICC/profile error appears.

7. Verify the configured printer/queue.

8. Send a small RIP/Print job.

9. Confirm that the printer actually receives and prints the job.

Check the resulting physical DTF print for:

• artwork dimensions;

• orientation;

• white layer/coverage;

• alignment;

• color;

• printer communication; and

• final output.

Keep your USB backup and original Windows installation until the entire workflow is verified.

We did not have to reconfigure the printer or Queue Manager

This is another important part of our result.

In our setup, we did not need to add the printer again, change the printer assignment in Digital Factory Queue Manager, or rebuild the existing DTF queue.

The same physical printer was already being used successfully from both:

• our original Windows laptop; and

• Windows 11 running through Parallels on the Mac.

Because Windows inside Parallels could already communicate with the printer, the printer connection itself was not the problem during our Digital Factory migration.

Our existing Digital Factory queue was already configured as:

Epson ET-8550 DTF v2

Once we restored the complete Digital Factory installation to its original folder path and the existing helper, queue and ICC references could resolve correctly, we made no additional printer changes inside Digital Factory Queue Manager.

We simply sent the existing RIP/Print command, and the printer received and physically printed the DTF job through the already configured connection.

Our working sequence was therefore:

Printer already accessible from Windows 11 in Parallels
        ↓
Existing Digital Factory DTF queue retained
        ↓
Restore original Digital Factory folder path
        ↓
Image import works
        ↓
ICC/profile references resolve
        ↓
RIP processes artwork
        ↓
Send RIP/Print
        ↓
Printer receives the job
        ↓
Physical DTF print

Do you need to configure your printer again?

Not necessarily.

If your printer is already installed and working inside Windows 11 on Parallels, and the migrated Digital Factory queue still points to that working printer connection, you may not need to change anything in Digital Factory Queue Manager.

That was exactly the case in our workshop.

If Windows inside Parallels cannot already communicate with your printer, however, or if your migrated Digital Factory queue references a different printer, Windows port, driver or network address, you will need to resolve that connection separately.

A useful troubleshooting order is:

1. Confirm that Windows 11 inside Parallels can access the printer.

2. Preserve the existing Digital Factory queue configuration.

3. Restore the original Digital Factory application path and resources.

4. Test image import.

5. Test RIP processing.

6. Send a small RIP/Print job.

7. Confirm physical output.

8. Only modify Queue Manager if the existing queue cannot reach the printer.

For our migration, no printer reconnection, Queue Manager reassignment or new queue creation was required.

Fixing the Digital Factory PostScript Conversion Error

Why could Digital Factory open but refuse to import a PNG?

This was our first major clue.

Digital Factory itself launched on Windows 11 ARM, but importing artwork generated a:

PostScript Conversion Error

In our case, the configuration was still expecting:

C:\Digital Factory v12 Direct To Film Edition\Helper\cadlink.exe

Because we had initially copied the application to a different location, that expected path did not exist.

Correcting the helper path allowed artwork to be inserted again.

This is why "Digital Factory opens on my Mac" and "Digital Factory actually works on my Mac" are two different tests.

For a production workflow handling detailed artwork such as our Batman Knightfall DTF graphic or Hulk Smacking Ant-Man Avengers design, reliable artwork import, RIP processing and physical printing matter much more than simply reaching the application's main screen.

Fixing the "Missing ICC file" error

After resolving image insertion, we encountered another error:

Missing ICC file

Initially this sounds as if the ICC profile was never copied.

In our case, however, the required profiles were already present.

They were located under:

C:\Digital Factory v12 Direct To Film Edition\Rip\system\clinks\

Our configured queue referenced files including:

ISOcoated_v2_eci.icc
CIELab.icm
sRGB.icm
E8550DT2\C1 print mode calibration ICC.icm

The important lesson is:

A "Missing ICC file" message does not necessarily mean the ICC file is physically missing.

The software may be unable to resolve the saved location after the application has been moved.

Check:

1. whether the selected ICC profile actually exists;

2. the exact profile path expected by the queue;

3. whether the original folder structure changed;

4. whether your source installation used additional external profile directories; and

5. whether restoring the original path resolves the reference.

Do not substitute an unrelated ICC profile merely to make the error disappear.

The appropriate profile depends on the printer, ink, media and print mode being used.

What finally fixed Digital Factory V12 on our M4 Mac?

Our complete successful sequence was:

Original working Windows installation
        ↓
Copy complete Digital Factory folder
        ↓
USB drive
        ↓
Windows 11 Pro ARM in Parallels
        ↓
Restore the ORIGINAL Windows folder path
        ↓
Launch the local C: copy of PSQueue.exe
        ↓
Image import works
        ↓
ICC references resolve
        ↓
Existing DTF queue retained
        ↓
Send RIP/Print
        ↓
Printer receives the job
        ↓
Physical DTF print succeeds

For us, the crucial change was moving the complete application back to:

C:\Digital Factory v12 Direct To Film Edition\

and restoring the configuration associated with that layout.

Because the printer connection and existing DTF queue were already working in Windows 11 on Parallels, there was nothing further for us to change in Queue Manager.

This is also why we recommend copying the complete original folder from the beginning, rather than trying to reconstruct individual helpers, profiles or configuration files after errors appear.

Digital Factory V12 troubleshooting table

Does copying the Digital Factory folder install everything?

No.

A working Digital Factory application folder can still depend on components installed elsewhere in Windows, including runtimes, services, printer drivers or other resources.

Our particular migration did not require reinstalling Digital Factory components, reconnecting the printer or rebuilding the existing queue.

Both Windows environments were already able to use the same physical printer.

If Digital Factory reports a specific missing runtime or component, use the appropriate official installer or repair procedure rather than copying random DLLs or system files.

Fiery documents printer/device management through its Devices → Manage Devices documentation.

CADLink Digital Factory V12 on Mac: Frequently Asked Questions

Can CADLink Digital Factory V12 run on a Mac?

Yes, in our tested Apple Silicon M4 configuration.

We successfully ran CADLink (Fiery) Digital Factory V12 Direct To Film Edition under Windows 11 Pro ARM through Parallels Desktop 27.0.1 on a MacBook Air M4.

We verified application launch, artwork import, RIP processing and successful physical DTF printing through our existing printer queue after restoring the installation's original Windows folder structure.

This does not establish official native macOS support.

Does Digital Factory V12 work on a MacBook Air M4?

It worked in our tested configuration.

Familia Fabrica tested:

MacBook Air M4
macOS 26.1
Parallels Desktop 27.0.1
Windows 11 Pro ARM64
Digital Factory v12 Direct To Film Edition
v12.1.2 components
Epson ET-8550 DTF v2 queue

Our verified result covered application launch, image import, RIP processing, the existing printer queue and successful physical DTF printing.

Does CADLink Digital Factory work on Apple Silicon?

Our verified test was performed on an Apple M4 MacBook Air.

Apple Silicon Macs use ARM architecture, so Parallels runs Windows 11 ARM rather than the conventional Intel version of Windows.

Windows can emulate many Intel applications, but that does not guarantee compatibility for every Digital Factory component, printer driver or peripheral.

Will this work on M1, M2 or M3 Macs?

We have not tested M1, M2 or M3 Macs.

The folder-path problem documented here is relevant whenever an existing installation is moved, but our successful result should not be treated as verification of every Apple Silicon generation.

Our confirmed hardware is the Apple M4.

Does CADLink Digital Factory work with Parallels Desktop?

In our setup, yes.

Digital Factory V12 ran inside Windows 11 Pro ARM using Parallels Desktop 27.0.1 on an M4 MacBook Air.

More importantly, we went beyond simply launching the application: we imported artwork, processed it through the RIP and successfully printed a physical DTF job through our existing queue.

Does CADLink Digital Factory work on Windows 11 ARM?

Our Digital Factory V12 installation ran under Windows 11 Pro ARM64 through Parallels Desktop on an Apple M4 Mac.

Our test included application launch, image import, RIP processing and physical DTF printing.

That is our independently tested configuration; it should not be interpreted as a statement of official support for every Windows ARM configuration.

Do I have to add my printer again in Digital Factory Queue Manager?

Not necessarily. We did not have to.

Our printer was already installed and accessible from Windows 11 inside Parallels, and the existing migrated Digital Factory queue continued to reference that working printer connection.

After restoring the original Digital Factory folder structure, we simply sent RIP/Print and the printer began printing normally.

If your printer is not already working from Windows inside Parallels, you will need to resolve the Windows printer/driver/port connection separately.

Why does Digital Factory show a PostScript Conversion Error when importing a PNG?

In our migration, Digital Factory could not find its configured image helper because the application had been copied to a different Windows directory.

The configuration expected:

C:\Digital Factory v12 Direct To Film Edition\Helper\cadlink.exe

Restoring the expected folder structure recovered image insertion.

Other causes are possible, so check the error details and actual helper path before changing the artwork itself.

Why does Digital Factory say "Missing ICC file" even though the profile exists?

Because the problem may be the saved path, not the physical file.

Our ICC files existed under:

C:\Digital Factory v12 Direct To Film Edition\Rip\system\clinks\

but relocating the application disrupted references used by the existing configuration.

Restoring the original folder structure resolved the workflow in our setup.

Where are Digital Factory V12 ICC profiles stored?

In our installation, the relevant profiles were under:

C:\Digital Factory v12 Direct To Film Edition\Rip\system\clinks\

Your installation may differ, particularly if you use custom profiles or resources stored outside the main Digital Factory directory.

Always check the actual source installation before assuming this path is universal.

Where is PSQueue.exe in Digital Factory V12?

For our installation:

C:\Digital Factory v12 Direct To Film Edition\PSQueue.exe

If yours is elsewhere, inspect the Target field of the working Digital Factory shortcut on the original Windows computer.

Does Digital Factory have to be installed directly on C: instead of Program Files?

No.

Our source installation happened to use:

C:\Digital Factory v12 Direct To Film Edition\

Our migration failed after we changed that existing path.

The lesson is not "Digital Factory can never run from Program Files."

The lesson is:

Preserve the working source installation's expected path when migrating an existing configured installation.

Do I need a paid Digital Factory license for this?

We used an existing valid paid license.

We did not test Digital Factory's trial activation under Parallels, so this guide does not claim that purchasing a license will solve a trial, ARM, import or compatibility problem.

Use the vendor-supported licensing and activation process for your installation.

Is CADLink Digital Factory officially supported on macOS?

This article does not establish official native macOS support.

Our configuration runs the Windows application inside Windows 11 ARM through Parallels Desktop on an Apple Silicon Mac.

For official compatibility information concerning your particular Digital Factory version, printer and hardware, consult Fiery/CADLink or your authorized reseller.

From troubleshooting experiment to daily workshop workflow

The reason we documented this migration is simple: we needed the software to do actual work.

At Familia Fabrica, large graphic designs in our Fourth Wall collections are generally produced using DTF, while other pieces across the studio use embroidery or mixed production techniques.

You can see examples across our:

• DC Comics graphic apparel collection

• Marvel Comics graphic apparel collection

• 90s Nostalgic apparel collection

Individual large-format graphic examples include the Vintage Superboy-Prime vs. Batman Who Laughs T-Shirt, Batman Black Lantern Dark Nights Death Metal T-Shirt, Hulk Smacking Ant-Man Avengers T-Shirt and Emperor Victor von Doom Doomquest T-Shirt.

That ongoing production use is why we wanted to document more than "the application launches." For us, the meaningful test was whether artwork could enter the RIP, retain the existing production queue and ultimately come out of the printer as a physical DTF print.

Custom Digital Factory Print Modes for Light and Dark Garments Tested on Windows 11 with Parallels on Mac M4

If you want to skip some of the trial-and-error involved in building reliable DTF output settings, you can also purchase our custom-curated Digital Factory print modes for light and dark garments.

These print modes are developed around the workflow we use in our own production environment and are intended as carefully prepared starting points for high-quality DTF printing across different artwork types, including photographs, illustrations, detailed graphics and strong solid-color artwork.

Each package is prepared with carefully selected settings for:

• White ink behavior and underbase

• Light garments
  

• Dark garments

• Detailed and photographic artwork

• High-quality DTF production workflows

The goal is to reduce some of the trial-and-error involved in balancing whites, colors and artwork characteristics instead of relying only on generic default settings.

Light Garment Print Mode:
Buy the Light Garment Digital Factory Print Mode

Dark Garment Print Mode:
Buy the Dark Garment Digital Factory Print Mode

Light + Dark Bundle:
Get the Complete Digital Factory Print Mode Bundle

These are digital configuration products, not Digital Factory software, printer drivers or licenses. You must already own and operate your own properly licensed Digital Factory installation.

Print results can vary with printer condition, printhead, ink, film, powder, curing, garment and other production variables, so you should validate the settings with your own equipment before production use.

Final takeaway

If you are migrating CADLink / Fiery Digital Factory V12 DTF from a Windows PC to an Apple Silicon M4 Mac running Windows 11 ARM through Parallels, and the application opens but image import or ICC processing fails, check the installation path before assuming the problem is Windows ARM or Parallels.

Our actual sequence was:

Digital Factory opened → PNG import failed → PostScript Conversion Error → helper path was wrong → ICC error followed → complete original folder/path restored → image import worked → RIP worked → existing printer queue remained usable → RIP/Print sent → physical DTF print succeeded.

We did not have to reconnect our printer or rebuild the queue because the same printer was already accessible from Windows 11 running through Parallels.

The working executable in our setup is:

C:\Digital Factory v12 Direct To Film Edition\PSQueue.exe

and the key principle is:

Preserve the complete working Digital Factory installation and its expected folder structure when migrating it. If the same printer is already working inside Windows on Parallels, preserve the existing Digital Factory queue before changing anything in Queue Manager.

This guide records the exact configuration tested in the Familia Fabrica workshop on 9 September 2026. We will update it if we validate additional Digital Factory, Parallels, Windows or Apple Silicon versions.

For more about the workshop, read about Familia Fabrica. If you have a production or creative project, you can also contact our studio.

Use at your own risk. Back up your files before migration and independently verify compatibility with your printer, drivers, profiles and software license. To the extent permitted by law, Familia Fabrica accepts no liability for errors, data loss, downtime or damage resulting from following this guide.