Here's an overview of the main features, limitations, and process for importing an InDesign IDML file as a base template:
1. Are Hyperlinks supported in the Embedded Creative Templates Builder?
Hyperlinks are not currently supported in Creative Templates - Embedded. PNG and JPG formats are image formats, and image files themselves do not contain clickable areas or interactive elements like hyperlinks.
2. Do users have the option to upload their own files into an image field?
Yes, three options can be applied in any combination to allow users to add files to a template. Template admins can adjust both job restrictions and template settings (cog) to enable or disable this feature.
- Images saved to template
- Allow to upload from the desktop
- Allow to select Assets from the library
3. If users design an image field in a specific shape, will they then be able to select/upload an image and drop it into that particular shape?
If the image is inserted into a basic shape in an InDesign file, the import will reflect this in the editor; however, some readjustments may be required for the scaling and placement of the image. For best results, ensure the height and width of the image match the shape in InDesign. Images that are larger/higher than the shape will be auto-resized.
Alternatively, template admins can upload the selected images, already confined to the required shape, as PNG files to the template or the DAM, ensuring end users fit the image to the picture box correctly. For instance, the template provides five image options for users to choose from.
4. What colors are supported in the Embedded Creative Templates Builder?
The Creative ‘Embedded Templates are mainly suited to digital material; therefore, only RGB is currently supported.
In best practice, we recommend converting all placed elements to your brand-compliant RGB colour breakdown to control colour consistency across various elements. The application will convert these for you; however, there may be variations on the breakdown for several reasons, such as file format and current colour space.
It is recommended to update the swatches used in InDesign and other embedded elements to RGB accordingly before importing.
5. Does Embedded Creative Templates support InDesign text treatments?
Text styling should be applied within the Embedded Editor; regular, bold and italic are supported.
Creative Templates (Embedded) does not directly support InDesign's advanced paragraph formatting features; instead, it focuses on basic text manipulation and allows you to import InDesign files while retaining fundamental design attributes. While the importer can ingest InDesign files, the granular control over paragraph styles seen in the native InDesign application is not part of the Creative Templates (Embedded) editor functionality.
Img.ly is considering adding more formatting options as part of their roadmap.
6. Does Embedded Creative Templates support Leading and Kerning?
Leading and kerning are not supported.
While the importer can ingest InDesign files, the granular control over paragraph styles seen in the native InDesign application is not part of the Creative Templates (Embedded) editor functionality.
7. Users can use the brand library for users to pick images from, but can they also have the option to upload their own files into an image field?
Yes, this can be enabled in the template settings (cog). Three options can be applied in any combination to allow users to add files to a template. Template admins can adjust both job restrictions and template settings (cog) to enable or disable this feature.
8. How are PSD Smart Objects handled in InDesign?
An embedded PSD Smart Object is not supported as a direct import into Embedded Creative Templates.
Note: the optimization script does not support files in .psb format. These will need to be manually converted.. See the dedicated helpdesk article here.
9. What template file formats are supported for ingestion?
PSD and IDML file formats are supported for ingestion into Creative Templates (Embedded), alternatively, you can create files from scratch in the builder.
10. How should users place and link images?
Images should be embedded in the InDesign documents. Do not copy and paste images/files directly into InDesign. Best practice is to place images in picture boxes. The editor supports the following layer formats: .png, .jpeg, .jpg, .gif, .webp, .svg, and .bmp. Other formats that are in the InDesign document can be automatically converted using the optimization script (see instructions here).
11. How are Placed Vector Files, eg, Logos, supported?
.ai and .eps files will not ingest correctly without being converted to a supported file format first. The optimization script can convert these for you (see instructions here).
Alternatively, use .jpeg, .png, .webp, or .svg formats directly when placing logos. These links must be embedded in your InDesign file to be directly ingested.
12. What layer formats are supported by the editor?
The editor supports the following placed and embedded file formats: .png, .jpeg, .jpg, .gif, .webp, .svg, and .bmp.
Non-supported formats present as linked elements in the IDML file will be replaced with placeholder images. The IDML Helpdesk article outlines steps for preparing the IDML file before importing and automatically converting it into supported formats. Support for converting other formats can be investigated as needed.
13. Does Embedded Creative Templates support images with a clipping path?
Yes, the Creative Templates (Embedded) editor supports images placed/embedded in an InDesign file with clipping paths. The clipping paths are honoured when the IDML file is imported into the Creative Templates (Embedded) editor.
14. Does Embedded Creative Templates support InDesign drop shadows?
Yes, the editor supports drop shadows on design blocks, which are comparable to InDesign objects, allowing you to modify attributes like offset, blur, color, and visibility. Drop shadows need to be created in the Editor. While InDesign drop shadows are a specific feature within Adobe's layout software, the editor uses similar concepts and offers granular control over drop shadow properties for images, text, and shapes within its editor.
15. Does Embedded Creative Templates support overlapping images?
Yes, the editor supports overlapping images through its overlay feature, which allows you to place one or more images on top of a base image. Users can then control how these overlays are blended using different blend modes, such as "normal," "overlay," "hardLight," "screen," and more, to achieve various visual effects. You can add custom overlays from local resources or remote URLs, and configure their intensity and appearance through the SDK's configuration options.
16. Does Embedded Creative Templates support placed and embedded SVG files? Yes, Creative Templates (Embedded) supports the use of SVG files as assets, which can be placed and embedded within the inDesign file or directly within the editor.
Regarding SVG file support:
-
Vector Graphics:
SVG files are inherently vector graphics, meaning they can be scaled without loss of quality, which is beneficial for design and editing. -
Asset Management:
The SDKs do not provide built-in storage for assets. You need to manage your SVG files (and other assets) on your own backend infrastructure (e.g., Amazon S3, Google Cloud Storage, Firebase, or a custom server). -
Asset Sources:
You implement a custom asset source within the SDK that provides URIs (Uniform Resource Identifiers) to your stored SVG files. The SDK then fetches these assets using the provided URIs.
Regarding how SVG files need to be saved:
-
URI Accessibility:
The primary requirement is that your SVG files are accessible via a valid URI that the SDK can use to fetch them. -
"Embed" vs. "Preserve" (Illustrator context):
If you are exporting SVGs from design software like Adobe Illustrator, the distinction between "embed" and "preserve" relates to whether Illustrator-specific editability information is included. For general use within the IMG.LY SDKs, the "embed" option, which typically results in a smaller file size by removing this extra data, is usually sufficient and preferred for web or app deployment. The core vector data of the SVG will still be present and usable by the SDK.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article