Skip to content

Size Restrictions

This page provides additional information for the maxWidth and openFullMax properties of Asset.

The following table summarises the effect of these two properties across all combinations. The numeric values in the example column are illustrative.

#Has rolesmaxWidthopenFullMaxOpen (anonymous) accessAuthenticated accessThumbnails
1No00Any region, up to platform limitN/APer policy / up to platform limit
2No10000Any region, up to 1000pxN/AUp to 1000px
3Noany>0Same as 1 or 2 (field ignored)N/ASame as 1 or 2
4Yes00NoneAny region, up to platform limitNone
5Yes10000NoneAny region, up to 1000pxNone
6Yes0400/full/ up to 400pxAny region, up to platform limitUp to 400px
7Yes1000400/full/ up to 400pxAny region, up to 1000pxUp to 400px

When an image has no roles, openFullMax is ignored. Only maxWidth has any effect.

Anyone can request any region up to the platform-imposed limit (platform-configured, 5000px by default). This includes upscaling.

The platform maxWidth is added to the info.json automatically.

Thumbnails are created according to the thumbnail policy, limited only by the image size itself (or the system limit if reached).

Conforms to IIIF Image API behaviour for maxWidth. The size parameter of any request cannot produce an image exceeding the maxWidth bounding square. When the size parameter is max, the resulting image is confined to the maxWidth bounding box.

Thumbnails are created according to the thumbnail policy, up to the bounding square defined by maxWidth.

openFullMax is only meaningful when the image has roles. If the image has no roles, the value is ignored and the behaviour is identical to scenarios 1 or 2, depending on maxWidth. Setting this field when an image has no roles is not an error, as you may vary roles separately.

When an image has roles, the iiif-img delivery channel provides a probe service and related IIIF Auth services. The behaviour for open and authenticated access depends on the combination of maxWidth and openFullMax.

The image service has a probe and related IIIF Auth services. Only users with one or more of the image’s roles can see any pixels.

An authorised user with a role can make requests up to the platform limit.

No thumbnails are produced, whatever the policy.

5. Has roles, maxWidth=1000, openFullMax=0

Section titled “5. Has roles, maxWidth=1000, openFullMax=0”

The image service has a probe and related IIIF Auth services. Only users with one or more of the image’s roles can see any pixels.

An authorised user with a role can make requests up to the maxWidth limit (1000px).

No thumbnails are produced, whatever the policy.

The image service has a probe and related IIIF Auth services.

Any user, including anonymous, can see /full/ region requests that fit within the bounding square defined by openFullMax (400px). Only users with one or more of the image’s roles can see non-full regions or sizes larger than openFullMax.

An authorised user with a role can make requests up to the platform limit (as maxWidth is 0).

Thumbnails are created according to the thumbnail policy, up to the bounding square defined by openFullMax (400px).

7. Has roles, maxWidth=1000, openFullMax=400

Section titled “7. Has roles, maxWidth=1000, openFullMax=400”

The image service has a probe and related IIIF Auth services.

Any user, including anonymous, can see /full/ region requests that fit within the bounding square defined by openFullMax (400px). Only users with one or more of the image’s roles can see non-full regions or sizes larger than openFullMax.

An authorised user with a role can make requests up to maxWidth (1000px).

Thumbnails are created according to the thumbnail policy, up to the bounding square defined by openFullMax (400px), or maxWidth if lower (unlikely in practice, but not an error).