paged.IDML Reference
Master spreads & overrides

Master items and stamping

Which master items appear on an IDML body page and where — the master page at the same position, MasterPageTransform, ShowMasterItems and stacking.

Tier: ProProIIIreference

A body page shows the items of the master page in its own position, mapped onto it by MasterPageTransform, behind its own items.

In short A master item is never written into a body spread. It stays in the MasterSpreads/ part, and every body page that applies the master shows it. Four things decide what a page shows: AppliedMaster picks the master; the page's position in its spread picks the master page (first from first, second from second); MasterPageTransform maps that master page onto the body page; and the body spread's ShowMasterItems can hide the whole master layer. Master items keep their master's stacking order and sit behind the page's own items. Placing master items on a page this way is called stamping here.

Which master page feeds which body page

A master spread has pages of its own, placed in its spread space exactly as body pages are. A master item belongs to the master page its geometry falls on. A body page takes the items of the master page at its own position in its spread: on a facing spread, the left body page takes the master's left page and the right body page its right page. A one-page master feeds every body page that applies it.

So a master can hold a left-page folio at the outer left corner and a right-page folio at the outer right corner, and each body page gets only its own.

Two body pages apply a two-page master. Each receives the rule drawn on the master page in the same position, placed on its own page.

Spreads/Spread_uspread.xml
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<idPkg:Spread xmlns:idPkg="http://ns.adobe.com/AdobeInDesign/idml/1.0/packaging" DOMVersion="20.0">
  <Spread Self="uspread" PageCount="2" BindingLocation="1" ShowMasterItems="true" AllowPageShuffle="true" ItemTransform="1 0 0 1 0 0">
    <Page Self="upageL" Name="2" AppliedMaster="umaster" ItemTransform="1 0 0 1 -595.276 0" GeometricBounds="0 0 841.89 595.276" MasterPageTransform="1 0 0 1 0 0"/>
    <Page Self="upageR" Name="3" AppliedMaster="umaster" ItemTransform="1 0 0 1 0 0" GeometricBounds="0 0 841.89 595.276" MasterPageTransform="1 0 0 1 0 0"/>
    <TextFrame Self="uframeL" ParentStory="ustoryL" PreviousTextFrame="n" NextTextFrame="n" ContentType="TextType" AppliedObjectStyle="ObjectStyle/$ID/[None]" Visible="true" Name="$ID/" ItemTransform="1 0 0 1 -537.638 145.8237" FillColor="Swatch/None" StrokeColor="Swatch/None" StrokeWeight="0">
      <Properties>
        <PathGeometry>
          <GeometryPathType PathOpen="false">
            <PathPointArray>
              <PathPointType Anchor="0 0" LeftDirection="0 0" RightDirection="0 0"/>
              <PathPointType Anchor="0 400" LeftDirection="0 400" RightDirection="0 400"/>
              <PathPointType Anchor="480 400" LeftDirection="480 400" RightDirection="480 400"/>
              <PathPointType Anchor="480 0" LeftDirection="480 0" RightDirection="480 0"/>
            </PathPointArray>
          </GeometryPathType>
        </PathGeometry>
      </Properties>
    </TextFrame>
    <TextFrame Self="uframeR" ParentStory="ustoryR" PreviousTextFrame="n" NextTextFrame="n" ContentType="TextType" AppliedObjectStyle="ObjectStyle/$ID/[None]" Visible="true" Name="$ID/" ItemTransform="1 0 0 1 57.638 145.8237" FillColor="Swatch/None" StrokeColor="Swatch/None" StrokeWeight="0">
      <Properties>
        <PathGeometry>
          <GeometryPathType PathOpen="false">
            <PathPointArray>
              <PathPointType Anchor="0 0" LeftDirection="0 0" RightDirection="0 0"/>
              <PathPointType Anchor="0 400" LeftDirection="0 400" RightDirection="0 400"/>
              <PathPointType Anchor="480 400" LeftDirection="480 400" RightDirection="480 400"/>
              <PathPointType Anchor="480 0" LeftDirection="480 0" RightDirection="480 0"/>
            </PathPointArray>
          </GeometryPathType>
        </PathGeometry>
      </Properties>
    </TextFrame>
  </Spread>
</idPkg:Spread>

Neither rule is in the body spread's XML: both come from the master part.

MasterPageTransform

MasterPageTransform on a body <Page> maps the master page onto that page. It is six numbers, like ItemTransform, and is almost always the identity: the master page's top-left corner lands on the body page's top-left corner. A non-identity value shifts, scales or rotates the master layer on that one page.

ShowMasterItems

ShowMasterItems="false" on the body <Spread> hides the master items on all its pages. The flag belongs to the spread: InDesign ignores it on a <Page>. The same attribute on the <MasterSpread> does not hide anything on the body pages that apply the master; the two-page-spread example carries ShowMasterItems="false" on its master and InDesign shows the master's rules on both body pages.

Stacking

Master items keep their order from the master spread: the item written first is at the back. Groups on a master are shown with their members. As a whole they paint behind the body page's own items, so a background panel on the master never covers the page's text.

InDesign's own rule adds layers: a master item paints behind page items on the same layer, and still in layer order against items on other layers, so a master item on the top layer appears above page items on a lower layer.

Text on masters

A master text frame's story is laid out separately on every page that shows it. A folio holding a page-number marker therefore shows each body page's own number, and a running head holding a section marker or a running-head variable shows the value for that page. See text variables.

The MasterSpread element

Attribute · MasterSpreadValuesPagedpaged.set
ItemTransformnumber-listread · written
Nametextread · writtenname
PageCountintegerwritten
Selfidread · written
ShowMasterItemstrueread · written
BaseNameenum / reference / textwritten
NamePrefixenumwritten
OverriddenPageItemProps—not read
PageColor
in Properties
—not read
PrimaryTextFrame—not read
The 10 attributes real documents use most. All 10 attributes of MasterSpread →

Name is the composed display name (A-Master), made of NamePrefix (A) and BaseName (Master). PrimaryTextFrame names a master text frame that receives the text when pages are added automatically. OverriddenPageItemProps is editing bookkeeping and does not change the result.

In Paged: the master page is chosen by position, items are routed by the centre of their bounds (a large item that covers half a master page or more also reaches a page it overlaps), MasterPageTransform and the master spread's rotation are applied as full matrices, and ShowMasterItems on the body spread is honoured. Master items paint in the master's document order with groups expanded to their members, behind all of the page's own items regardless of layer. Group transparency and drop shadows on master items are not applied, and a master based on another master contributes only its own items.

Supported · verified Supported · verified

The next page covers what an override removes from this.

Frequently asked questions

Why don't master items appear in the body page's XML? Because pages inherit them. They stay in the MasterSpreads/ part; only an overridden item gets a copy in the body spread.

Which master page does a body page use? The one at the same position: the first page of a body spread takes the master's first page, the second takes the second. A single-page master feeds every page.

Does ShowMasterItems on the master spread hide its items? No. The body spread's ShowMasterItems decides whether its pages show master items. InDesign ignores the attribute on <Page> and the master's own value does not hide items on body pages.

Do master items render behind the page's own content? Behind the page's items on the same layer. Across layers, the layer order still applies in InDesign.

Are grouped master items shown? Yes. A group on a master reaches the body pages like any other master item.

On this page