Document Presets vs New Page Sizes.xml: Adding page sizes

A recent forum post concerning adding page sizes to InDesign’s Document Setup highlighted two different ways to accomplish this task. This article will explain both methods, and the strengths and weaknesses of each method as while they both perform similar tasks, they are not the same and can complement each other.

First method: Saved Presets

Before beginning, it is worth noting that when making a new document in InDesign, users will be presented with one of two different interfaces. In the latest version of Creative Cloud, the default user interface looks like this:

There is also the Legacy interface that long-time InDesign users will be more familiar with:

To choose to use the Legacy user interface, go to the InDesign Preferences (Command+K for Mac, Control+K for Windows) and check the Use Legacy “New Document” Dialog checkbox on. Alternatively if the new default look is preferred, uncheck the dialog box.

Making a saved preset in the default “New Document” dialog

Go to the New Document dialog box (Command+N for Mac, Control+N for Windows) to show the user interface.

Once open, go to the right hand side of the dialog box and enter the measurements, orientation and other desired options.

To save the preset, click on the icon to the right of the Preset Details heading and a new prompt will appear to save the preset.

Once named and saved, the preset can now be accessed in the Saved portion of the user interface.

Be careful in this window as deleting a saved preset will remove it without prompting for a warning.

Making a saved preset in the Legacy dialog

Go to the New Document dialog box (Command+N for Mac, Control+N for Windows) to show the user interface.

Once open, enter the measurements, orientation and other desired options. To save the preset, click on the icon to the right of Document Preset dropdown and a prompt will appear to save the preset.

Once named and saved, the preset can now be accessed Document Preset dropdown of the user interface.

The preset can be deleted by clicking the trashcan in the top right corner of the dialog box, but unlike the default interface, a warning dialog is presented.

Managing saved presets

Regardless of the interface used to make the preset, they are managed by going to the File Menu, Document Presets, then Define. This will present a new dialog box:

From this dialog box, it is possible to save presets so that they can be shared with others as a .dcst file; load preset .dcst files that others have created, as well as make new presets, edit or delete existing presets. Again, a warning will be presented if a preset is to be deleted.

Note though that when making a new preset or editing an existing preset that the Legacy dialog box is used.

Second method: New Page Sizes.xml

This other method calls upon an XML file that InDesign references for custom-made sizes. On a Mac, it can be found here:

InDesign/your_version_of_indesign/language_installed/Page Sizes/New Page Sizes.xml

/Users/JohnCitizen/Library/Preferences/Adobe InDesign/Version 14.0/en_US/Page Sizes/New Page Sizes.xml

This file can be edited to add custom sizes. By default, the XML file looks like this:

The syntax to create a new page size looks like this:

The <Name> tags refer to the name of the page size that the user will see in the New Document dialogs. The <Width> and <Height> tags refer to the measurements and these measurements are in points. Each page name, width and height are wrapped in their own <PageSize> tag.

For this example, I’ve taken in all A, B, C, D paper sizes as well as some imperial sizes and saved the XML file.

Anyone interesting in having this file can do so by downloading it here.

When I now open the default New Document interface, the new options now appear in the Print portion:

And here is what it looks like in the Legacy user interface:

Distinctions between Document Presets and New Page Sizes.xml

  • The default user interface will allow users to add Document Titles to new documents and also allow users to see page sizes at a glance, as opposed to the Legacy interface where page size measurements are only visible once a preset or page size is selected from the dropdown.
  • Selecting Create Alternate Layout from the Pages panel will show a new dialog box that contains pages added via the New Page Sizes.xml file. These page sizes will be able to be selected from the dropdown, while page sizes made via the saved presets will be unavailable.
  • The New Page Sizes.xml will only add names of page sizes, widths and heights; while adding presets stores more information such as total number of pages, page orientation, page size (including pages that can be accessed from the New Page Sizes.xml), amount of columns, margin dimensions, bleed and slug settings, and whether to have facing pages or primary text frames.

Add a “Night” mode to InDesign

In the same way that different political or religious views can polarise a group of people, so can one specific InDesign feature: Light or Dark interface.

Introduced into InDesign CC in 2013, this change brought InDesign in line with other Creative Cloud products that had a dark interface. That said, I was not a fan and chose to remain a user of the light interface.

Many years later and Apple released the macOS Mojave with its Dynamic Desktop and Dark mode. The Dynamic Desktop feature shows a bright desktop during daylight hours and a dark desktop during the dark hours. In addition, popular apps also followed suit allowing users to switch from the usual view to a “night mode”.

In addition, I have found myself working late into the night on projects, and have found that a darker interface during these hours is easier on my eyes. That said, I still like to use a light interface when working in daylight hours.

With this in mind, I wondered if it was possible to create an InDesign startup script that – upon performing a common task such as opening a file – would check the time of day and if it was beyond a certain time of the day, would invoke the dark interface… and it was.

I’ve now added this script to the site and it can be downloaded from here or the scripts/download pages. As this is a startup script, it has to be added to the Startup Scripts folder (see Ole Kvern’s excellent instructions for doing so here).

The script can also be modified to suit by going into any text editor such as textedit or notepad and editing the following lines of the script:

if (hours <= 7 || hours >= 18)

This indicates the hours of the day. In the script, 7 = 7:00 am, and 18 = 6:00 pm.

app.generalPreferences.uiBrightnessPreference = 0.0;

This refers to how dark the interface should be. 0.0 is totally dark, 1.0 is bright, but values from 0.1-0.9 can be used as well.

app.generalPreferences.pasteboardColorPreference = 1; 

This refers to the color of the pasteboard. The number 1 will match the pasteboard color to the interface, whereas 0 will leave the pasteboard white.

So technically it’s not a night-mode per se, but for those who like the light interface until the night-time hours, this script may be something to consider.

Droplet like it’s hot

As a prepress operator, a great deal of my time is spent making sure that artwork supplied by clients will print without any prepress issues. Given that most client-supplied files are PDFs, a great deal of my time is spent in Adobe Acrobat checking the files using the print production tools and an invaluable plug-in called Enfocus Pitstop Professional.

While I’ve given the Adobe Acrobat team plenty of grief over my last few blog posts, I do have to sing their praises over a rather massive feature that – for me at least – has gone unnoticed since its inception in Acrobat 7 – preflight droplets.

What is a droplet?

A droplet acts as a “hot folder” that – once a PDF is dragged onto it –  will run a preflight profile on that PDF.


This works for one or many PDFs. I first learned of this feature from this Jean-Claude Tremblay’s post to an InDesignSecrets article about using the preflight feature to convert a file to outlines, rather than using InDesign-based methods. That said, the droplets feature has been available since at least 2007!

Making a droplet is simple. While in the print production panel of Adobe Acrobat, click the preflight button, and in the new dialog box, select Create Droplet… from the Options button.


The next dialog box will ask what preflight profile to use, where success/failed PDFs should be processed to, and if a summary PDF needs to be created of each file.


Many of the built-in preflight profiles either force compliance to one of the PDF/X standards, or analyse a PDF and report the errors that were encountered. However, it is the custom fixup portion that may interest readers in a production role. To see where this can be found, click the Edit Profiles… selection from the Options button of the preflight dialog box.


Underneath the warnings and standards compliance, there is a section titled custom fixups.


In this panel is a plethora of changes that Acrobat can make to an entire document to fix common preflight issues such as:

  • Faux blacks
  • White overprint, or other colours that should knockout instead of overprint
  • Black instead of Registration
  • Remove trim marks and take back to 3mm bleed
  • Make pantone spot color names consistent

In addition, it is possible to make your own custom fixups rather than use the built-in ones. Click the add button to add your own fixup.


It is also possible to drill down even further in the editing by clicking additional edit buttons.


This allows for further variables to be made.


Usually, many of these changes would be done using Enfocus Pitstop Professional’s action lists or global changes, but with the creation of an appropriate preflight droplet, not only can they be done without the Enfocus Pitstop Professional plug-in, they can also be done without opening the PDF.

Wouldn’t use it as a catch-all

It would be great to have one preflight that will catch all scenarios and fix the PDFs so that all that needs to be done is make sure the content is right and that the art is fit for its purpose… but because there are so many edge-cases that I deal with, it is more appropriate to make a “catch-most” preflight for common errors such as the ones mentioned earlier.

It can be confusing

With so many options to choose from, it can also be very confusing and – at times – frustrating, especially when some custom fixups contradict each other with no way of being able to sort out what one should go first.

Some of the commands are also not so intuitive. One instruction that I wanted to use – that was to make any object that wasn’t 100% black to knock out – wasn’t where I thought it would be.


It took hours of trial and error to realise that the color range to select was Gray Object (black below 96%) is set to overprint… but who would know with the other options that appear to make more sense?


It’s not a magic bullet

That’s not to imply that the Enfocus Pitstop Professional plug-in isn’t necessary – it is an absolute must for prepress operators. Preflight droplets complement the Enfocus plug-in, saving hours of time manually scanning a PDF looking for “the usual suspects” and allow PDFs in a workflow to be “normalised” for colour profile, trim/bleed size, appropriate overprints and knockouts as required, etc.

There are some fixups that work better using the Enfocus Pitstop plug-in, such as the generate bleed action. When run as a custom fixup via Acrobat preflight, it only adds bleeds to rendered art, and usually by scaling it. The Enfocus pitstop plug-in is more versatile in that it will apply to both vector and raster images, and bleed off appropriate edges only.

Importantly, the preflight fixups won’t be able to make content-related changes, such as fixing typographical errors or moving artwork away from a trim-edge… these changes have to be made with manual intervention using the Enfocus tools.

Lastly, preflight droplets are not a substitute for a skilled prepress operator examining a file, given that droplets cannot:

  • Ensure that artwork will fold correctly or be suitable for their intended purpose;
  • Confirm that the artwork is the correct version supplied by the client;
  • Understand the context of the content such as spelling, grammar or “design features”.

Is this why Data Merge PDFs are “throttled back”?

Some time ago, I wrote an article about the difference between Data Merge PDF Export vs regular PDF export. The article highlighted the difference between the two PDF exports, but not why the data merge PDF export appears to have been throttled. Admittedly, this seemed more of a curiosity than anything else, and no further research was undertaken.


The Data Merge PDF export dialog box. The yellow highlight shows items that can’t be checked.

In October 2018, the issue was once again raised by a reader who asked about preparing tagged PDFs via the Data Merge palette for the purposes of Section 508 accessibility – a way tagging a PDF so that PDF-reading software with accessibility features can assist users with limited accessibility in various ways, such as the example of tagging an image with a description that can be read aloud for users with little- or no vision.

As I couldn’t offer an explanation, all I could do was point to my previous article and submit a request to the InDesign Uservoice team to allow the Export to PDF to have all features of a regular PDF.

Then one month later, I fielded a query on the Adobe InDesign Forums concerning Interactive PDF and Data Merge Conflict where a user had hyperlinks in an interactive PDF where data merge fields were present, even though they weren’t linking to anything.


Notice the tooltip displayed by the name “Zolly” – text that was a Data Merge text field.

That reminded me of an article from InDesignSecrets about Ghost Hyperlinks explaining that data merge fields can also be shown in the hyperlinks panel, meaning merge fields are hyperlinks themselves.


The highlighted field in the art is the data merge field, as well as hyperlink 2.

However, Data Merge can’t export to interactive PDF from the data merge panel, so the only way I could replicate the forum poster’s issue was to prepare an InDesign data merge file, navigate to a relevant record,  then go to the file menu and export an Interactive PDF of the visible record on the page.

It was at that moment it occurred to me that THIS may be the reason that the hyperlinks checkbox is greyed out from the “export to PDF” dialog box in the data merge palette – because the merge fields are – in effect – hyperlinks themselves, and having hyperlinks enabled would also make the variable text clickable in the resulting PDF, despite having no actual link to go to. It would also explain why data merge does not offer an “export to interactive PDF” option from the data merge palette.

So, despite having a “eureka” moment of solving why the exports were different, it also made me realise that – without overhauling the way data merge works in InDesign – it may be unlikely to directly export PDFs with hyperlinks or interactivity via the Data Merge Panel anytime soon.

It is worth noting that if the data merge is exported to an InDesign file first (as explained in my workaround linked at the start of the article), and then exported to an interactive PDF, these issues do not occur. However, it is double-handling.

Still, this is frustrating in a world moving online, particularly for marketers who want to prepare unique PDFs that contain:

  • Hyperlinks, not just for navigating to URLs, but within the PDF itself, such as footnotes or page navigation;
  • Interactivity such as form fields for the purposes of surveys and feedback; and
  • Accessibility, not only from the legal standpoint of Section 508 conformance, but the genuine desire to engage with people with limited accessibility.

On that note, isn’t it about time to update the data merge feature so that exports are no longer limited to throttled-back PDFs or InDesign files as their only options? As an addition, how about the ability to print a merge directly from a data merge file, a feature that has been available in Microsoft Word for nearly thirty years.

Or what about the ability to merge to uniquely named files based on each record, something that I’ve already prepared a script for but would welcome as part of the InDesign user interface. And why stop at full-throttle PDFs… how about image formats such as jpg or png, or other formats such as html? Statistics from an InDesignSecrets poll show that print PDFs account for just under half of the participants’ usual file output exports.

%d bloggers like this: