Mastering Presets in Print-Tool 2.4.0
Updated Halloween, 2026: Now that Roy Harrington has worked out how to bring a lot of sanity back to the processes of both creating new printing presets and using printing presets, Print-Tool can, for the first time, since the advent of macOS Ventura, be used reliably, for both aspects of using the handy Apple feature of user-saved printing presets. https://www.quadtonerip.com/html/QTRprinttool.html
And thanks to Tracy Valleau for digging up the original observation of the hollowed-out (incorrectly saved) “Print Job” presets while looking at this, year before last, which, in turn led to the pointers given below. Recently, he and I have been helping Roy figure out how to get Print-Tool around this preset bug and some other issues. Print-Tool is looking really good now. After more than three and a half years, Apple is woefully behind on fixing this preset bug, hopefully not for much longer. When they do, Print-Tool 2.4.0 is also expected to keep working correctly without requiring further adjustment.
What preset bug, is that, now? First, presets are distinct from the “Default Settings” which are not user-created sets of print driver settings but which form a similar, system-supplied group of many dozens of settings (in the case of the EPSON pro printers), derived from settings data supplied by your installed printer driver, and thus from the manufacturer of the printer.
Here’s the problem: with OS Ventura, macOS 13, Apple merged elements of macOS and iOS, replacing much of the printing pipeline code. Presets were, prior to Ventura, a handy way to save a complete set of all printer driver settings for a desired configuration of your printing pipeline. In Ventura, they added a second kind of preset. They call the original, complete kind “Print Job” presets and the new subset of changed settings only kind “Custom” presets. Even the names are wrong, because both types are equally custom and both types are equally for print jobs.
For the Epson wide format printers, a full Print Job preset contains on the order of 80 to 90 entries. A Custom preset contains only a few, depending on how many settings you changed after starting with a full Print Job preset or after starting with the “Default Settings”. There might be only a half dozen entries, for example. We can imagine that somebody thought it would be efficient to avoid recording redundant data, but failing to record all the settings in each of even an extraordinary number of saved presets, say dozens, for one type of printer would still consume what today can only be considered a tiny bit of data, so I would argue that this was a big mistake. Penny wise and pound foolish.
The next problem is that a bug is also in the new code starting with Ventura, which in many circumstances results in a Print Job preset being saved as though it were actually a Custom preset! I.e. grossly defective. This leads to catastrophic failures to print correctly. This bug is avoidable as I’ll describe below, by only saving your Print Job presets in certain ways. But it’s also important to be able to clearly and directly see for yourself when a preset is defective by actually reading the .plist file that incorporates it. Tracy discovered this problem by doing exactly that. Further down I explain two pretty easy methods to inspect your saved presets. One thing I can’t help you with is to tell you how many items should appear in a full preset for each kind of printer. Some printer drivers probably have far fewer items / settings in them than the professional class of EPSON printers do, most likely by virtue of being an entirely different kind of machine, say a laser printer, where this issue is unlikely to matter anyway.
Please also read Roy’s essay about this topic here: http://www.quadtonerip.com/Printer-Presets.pdf
Whenever the bug that currently remains in macOS Ventura through Tahoe inadvertently causes a saved “Print Job”, i.e. complete, preset to be saved as a super-incomplete, i.e. partial “Custom” preset instead, a potentially terrible problem is queued up, because when you go to use that Print Job preset, something like 90 percent of the required settings are missing. So the OS automatically loads in a wrong group of settings. I can’t say exactly which ones, but it’s likely to be the so-called system-supplied Default Settings except for those settings which were recorded in the incomplete Print Job preset which was actually, in effect, a Custom preset. Those Default Settings are stored in CUPS (the Common UNIX Printing System) that handles a lot of printing services for macOS. Those settings can be accessed via browser and even edited, but in my own experimentation with that, there appeared to be no benefit to either preset performance or color management results from making any type of edits to those settings, despite several experiments done along those lines. Tracy reported success with that, but I tried to repeat his experiments and more and found zero benefit.
Here are two great ways to let you instantly see for yourself what a preset contains. If you look into an intact, complete, normal and correct Print Job preset and a saved Custom preset, you should see a huge difference in the number of settings stored. All your presets of a given class are stored in one .plist file in one of the two locations shown, where the tilde (til’duh) means this is the Library folder in your Home folder, not the root level Library folder that sits beside the main System folder. So you may have two or three or more .plist files, each with some number of presets stored within them, depending largely on how many printers you've got.
~/Library/Preferences/com.apple.print.custompresets.plist
or
~/Library/Preferences/com.apple.print.custompresets.forprinter.[name of your printer].plist
That first .plist file path is where presets are saved when they are saved for All Printers. I now prefer that option over saving a preset only for a given printer, in case we might replace (and re-name) our “printer” (not the actual hardware, rather just the installed one shown in the Printers & Scanners system setting), then we get to keep our presets instead of having to re-make them from scratch. On the other hand if you use lots of different actual printers, different machines, then a benefit of saving your presets for only one printer will be that the list of presets for a given printer in the printing UI will be a lot shorter and thus easier to peruse. Both options seem to work fine now, at least when printing from the new (as of February, 2026) Print-Tool 2.4.0. If you use Print-Tool, by all means make certain you're using version 2.4.0, though if you're still on Monterey or earlier, then 2.3.4 should still be OK.
Until the upgrade of Print-Tool to version 2.4.0 from version 2.3.4, it had become necessary to only save new presets in Preview app when using Ventura or later, because they always save correctly in Preview. Most other applications from which one might print via macOS Ventura or later are not capable of matching Preview in this regard! Preview also works well with respect to using such presets, but Preview lacks some important features for printing, so it’s certainly not the greatest overall candidate as a printing-capable tool. Lo and behold, ColorSync Utility is significantly more full-featured than Preview as a printing application, albeit with a rather kludgy interface that makes it unnecessarily difficult to be certain of what it’s doing and therefor exactly how we need to use it. That’s another long story.
And for what it’s worth, the latest version of Photoshop, v27.3.0 as of today, February 13th, 2026, is also still hobbled with broken presets and other problems as well, though it usually works fine for actually printing if you are converting to the printer profile during the printing versus converting ahead of time (it’s not printing correctly on one of my two Sonoma M1 Macs, for color management reasons, when I'm printing that way, but that’s another story). In other words, if you are printing from Photoshop, you must use Preview app to save any and all new presets, rather than using Photoshop itself to do so! This avoids the Preset Bug that is likely to give you a Custom preset masquerading as a Print Job preset. Print-Tool 2.4.0, on the other hand, does let us reliably save new Print Job presets which are correctly built, just as Preview app does.
So, there are two tidy ways to easily read the relevant contents of any of the .plist files located at the paths listed above. One is to buy a $7.99 program for macOS from the App Store called PLIST Editor and the other is to download from Apple and install the latest version of Xcode that’s compatible with your version of macOS (link below, free account setup required).
Xcode is a huge program that will take up over 12 GB of space on your Mac, but either program can easily be set in a Finder Get Info window as the default application for opening .plist files, so that you just double-click the .plist file (if it’s Xcode, once to launch Xcode then once again to open the file) and voila: you get to instantly see the critical facts of any of the printing presets on your system. Very handy. In the second and third figures below, you can see how Xcode presents the info and one version of how PLIST Editor presents the info. Note that having opened the .plist file in Xcode, you first look down the list of items inside the .plist file for the one named the same as your preset (each .plist file contains all your saved presets of a given class, e.g. the ones you’ve saved for All Printers or the ones you’ve saved for any particular printer). Then you hit the expansion arrow (>) to see inside of its first layer, then read this line:
“com.apple.print.preset.settings”
That line also contains the word “dictionary” and a number “(XX items)”. If that number is in the range of 80-something to 90-something, your preset is a good one, i.e. a complete “print job” one, at least in the case of an EPSON wide format printer. If the number is something like 6 or 10 or perhaps even 30, it’s a bad one if it's supposed to be a Print Job preset or it's a Custom preset, again those are typical numbers for the case of an EPSON wide format printer. But double-check with your printer that this appears to make sense. For example, save each of a Print Job preset and a Custom preset in Preview app, either for All Printers or just for the one printer, then open up both of those two new presets and compare the number of saved items. That should unambiguously teach you about how many saved items a complete Print Job preset should contain for your printer. But it is true that they vary in length. Some might contain about 80 items and some about 90, for example. That's OK.
Any preset saved as a “print job” preset that meets that rough numerical requirement is one that will work in Print-Tool 2.4.0 when you select it to cause all your preferred settings to be loaded in as intended. Once you’ve accomplished that in the Print Settings inner UI (meaning the UI that Apple builds, customizing it for your printer driver’s inputs), if you hit Print, those will be the settings that are actually used to make the print. You get to this inner UI in Print-Tool 2.4.0 when you hit the Run Print button. It used to be the case that you also got to it by hitting the "Page Setup: Paper & Print Settings..." button, in earlier versions of Print-Tool as well as when you hit the "Run Print" button. Now when you hit the upper button "Page Setup: Page Setup..." you don't get into those settings, rather you only get the actual Page Setup interface, where you choose the printer, the paper size, scaling percentage and orientation. Better!
This way of scoping out preset integrity is more reliable than just snooping around in the printing UI, though that can often tip you off that something is very wrong, because you see wrong settings loaded in, especially as a result of being in one of the inner dialogs and hitting Cancel to exit that inner dialog. This often results in the Default Settings getting loaded! You see that when you re-enter the inner dialog right after having exited it by hitting Cancel. Hitting OK never triggers this “Cancel” bug, as I call it. This is another disgraceful bug that should have been immediately fixed by Apple and which as of February, 2026 was still happening even in the latest version of the OS, despite three years having passed since the bug was created. Shame on you Apple, for doing such a lousy job of debugging macOS of late! I see way more buggy crap in macOS lately than I ever have over the last 34 years of using it. And I’m not even sure that official channels bug reports aren’t just getting ignored. It really pisses me off, frankly. I don’t mind helping people get their code working right, even when I’m not doing beta testing, but when gross and well-known bugs are ignored for month after month and year after year, that’s disgraceful. And these two bugs are only two among several that plague the macOS printing pipeline.
Here is the Printer Options > Printer Settings dialogue for an EPSON SureColor P9000 Standard Edition in my preferred configuration for running certain color management debugging tests of late. When my printer’s built-in Default Settings are loaded, either intentionally or because a bad preset is used or because the Cancel bug occurs, just about everything here changes, so it’s super obvious when I look back into the dialog after just having left it, either by hitting Cancel or by hitting OK, whether things are good or not.
Again, in Print-Tool 2.4.0, even that nasty Cancel bug appears to have been fixed, but beware of it nevertheless. But it wasn’t fixed by anything Apple did, proving that the bug has to do with an interaction between third party printing apps and OS code. Apple needs to take more responsibility in such situations. When they change the underlying architecture that other code depends on and they figure they can’t avoid this resulting in a problem, they should aggressively assist the people who make the third party printing applications change their code accordingly. Go back into dialogues that you just left, just to check that the settings you see are the same as they were when you closed the dialogue. Hitting OK in those UI locations where the choice is Cancel or OK is always safe (unlike hitting Cancel), assuming you want to accept any changes you made in one of these inner dialogs! Hitting Cancel might nuke your settings.

And here’s what one of my .plist files looks like on the inside just now, from a period of experimentation with preset debugging, as seen in Xcode 16.0. My preset was named “9K PPWSM TEST 6” and the critical info is “83 items”.

If you flip the expansion arrow (>) in that same line, the entire list of 83 items (and then some) opens up.
Go here to download Xcode if you prefer, versus using PLIST Editor, which can provide a very similar view of the inside of your .plist files:
https://developer.apple.com/download/
The version of Xcode found in the App Store is only for the most current versions of the OS. I’m using Sonoma now (nowhere near current, but preferred), so I had to download my version from the developer site.
Here’s one way the list can look in PLIST Editor, i.e. pretty much the same (adjust the UI if needed to see this arrangement):

I agree with Roy’s sense that it’s best to stick to using “Print Job” presets. As to whether keeping “Reset Presets Menu to Default Settings After Printing” enabled is still necessary, it might be, but I think the latest Print-Tool versions of the last couple of weeks, including 2.4.0, have been working right, even without doing that, I’m not absolutely certain — try it and see, but it seems to be working fine either way in Print-Tool 2.4.0 (which is still current as of October 30, 2026 as I make a bunch of edits to this article). At one point it was necessary to re-launch Print-Tool prior to saving any new preset, but that issue has been fixed too.
So Happy Presetting!
PS: On the matter of color management going wrong in macOS printing, I hope to have a lot more to say in another article, on account of two important bugs that cause incorrect results by leading to superfluous and incorrect profile-to-profile conversions being applied to data which has already been correctly prepared for printing, totally ruining the printed result.
These bugs occur in certain pathways, as I’m calling them, ways to get correct color management while printing. For example, across just four printing applications: Print-Tool, ColorSync Utility, Preview app, and Photoshop, I count 23 distinct ways to print which should all result in correct color management. Many of those ways do not, but even worse, the number that do not is not always the same from Mac to Mac, even my two Macs of the exact same M1 vintage, the exact same OS and using the exact same software for printing. So the color management picture is complex and especially difficult to diagnose.
Most users will find that the pathways that rely on Print-Tool’s options of either “Print Tool Managed” or “No Color Management” work correctly. One of the four pathways that rely on Print-Tool’s third of three options “Print Driver Managed” does not work correctly, and that exact same path in each of the other three printing applications also fails to work correctly, making it clear that this is almost certainly Apple’s fault. Neither Print-Tool nor Epson’s driver likely have anything to do with this failure but investigations are underway to attempt to clarify the situation in the faint hope that these bugs can get fixed once somebody at Apple learns about them. How could they not have known about this mess for years, with millions of users? For the record I've run some of these many, many potential tests on a third Mac, an M4 iMac running Tahoe, macOS 26, and found no improvement. I've also had colleagues running Tahoe check for different improvements and find none.