What's New in CHILI GraFx

GraFx Studio 1.47: Overprint for Print Output and More Control Over Shape and Component Frames

A black headline on a magenta panel looks sharp on screen. On press, the printing plates can shift by a fraction of a millimeter and leave a thin white line around every letter. GraFx Studio 1.47 adds overprint to prevent that. It also lets designers set how much freedom end users have on more frame types.

---

Overprint for Cleaner Print Output

With overprint, one ink prints on top of another instead of knocking out the inks underneath. The press no longer leaves a gap in the ink below, so small misalignments between plates don't show. This helps with black text on colored backgrounds, fine strokes, and barcodes on colored panels.

• Frame-level toggles: You can turn on overprint for fill and stroke on text and shape frames, and for fill and background on barcode frames.
• Print layouts only: Overprint only works on spot colors whose secondary color is defined in CMYK.
• Precise text control: You set overprint on selected text, not the whole frame, so one frame can mix overprinted and knocked-out type.
• Written into the PDF output: Your production partner gets exactly what you set.

Explore Overprint

---

Set End-User Freedom on Shape and Component Frames

Text and image frames already let designers decide what end users can change. Shape frames and component frames now have the same settings. Designers choose whether end users can move a frame horizontally or vertically, rotate it, or resize it, with the option to keep its proportions.

These rules apply in Design mode, Run mode, and Studio UI, so the design system stays intact wherever people work.

Learn how user freedom settings work

---

Other Improvements

• Copyfitting: New templates default to a maximum of 10000%. Copyfitting
• Corner radius: Fields show the layout unit (px, mm, or in) and highlight the corner you're editing. Corner radius
• Justified text: The last line of a paragraph no longer stretches.
• Greek final sigma: A standalone σ' no longer turns into ς'.
• SDK: getLayoutsWhereFrameIsVisible returns the layouts where a frame is visible, and updateFrameGradientSettings accepts start and stop points.

---

What's Fixed

This release fixes more than 20 issues, including:

• Fonts: Fonts load faster and use less memory. Glyph shaping in CFF fonts is fixed, and marks sit more accurately in scripts such as Telugu.
• Brand Kit sync: The canvas now updates when a sub-theme is selected.
• Component mapping: Data source mapping is more reliable, and mappings are validated before any values reach the canvas.
• PDF output: Internal errors that could make PDF output fail on specific templates are fixed.

Read more in the Developer Center

CHILI GraFx Environment API: Brand Kit Text Styles Now Come With Usage Guidance

A style called "Heading 2" tells you how text looks. It doesn't tell you when to use it.

Brand Kit media and colors can already carry an optional description. With the latest CHILI GraFx Environment API release, paragraph styles and character styles can have one too. This means usage guidance now stays attached to your typography.

---

Usage Guidance That Stays With Each Style

• Optional description: Paragraph styles and character styles accept a free-text description, such as "body copy, for long-form text".
• Shared across themes: A description belongs to the element, not the theme. You set it on the default theme, and every theme of the Brand Kit shares it.
• Returned in the resolved theme: Every tool or integration that reads the Brand Kit sees the same guidance.
• Existing Brand Kits unaffected: Existing Brand Kits work as before, and styles without a description return none.

Descriptions also give GraFx Genie the context that a name alone can't provide, so it can pick the right style for a given design. That feature isn't available yet.

---

What's Fixed

Output generation no longer fails on assets whose preview showed as ready but was never actually created. A preview that returns no result now counts as a failure. The problem shows up straight away instead of breaking the output job later.

How descriptions fit into a Brand Kit

Read more in the Developer Center

GraFx Studio 1.46: Editor Load Fix for Chromium 152

When Chromium 152 reached stable release at the end of August 2026 and rolled out through automatic browser updates, the GraFx Studio editor stopped loading. That is fixed in GraFx Studio 1.46.

---

What Was Happening

On Chromium 152, the editor failed to load on both macOS and Windows – and it applied everywhere the editor runs: the Studio workspace in CHILI GraFx, GraFx Experience, and custom integrations built on Studio UI or the Studio SDK.

The cause was a change on the browser side. The fix is on ours, so no browser setting or downgrade is needed.

Nothing was lost. The issue occurred only while loading the editor – templates, projects, and their content were never affected.

---

What You Need to Do

The fix requires version GraFx Studio 1.46 or later. If your environment runs on an earlier version, the editor still fails to load in these browsers.

1. Update the GraFx Studio version in your environment settings.
2. If you run a custom integration, make sure it loads the matching Studio UI or Studio SDK version.

Manage your environment version

Versioning your integration

Browser support for CHILI GraFx

Figma Designs Become GraFx Studio Templates – Experimental Plugin 0.8.0

Figma is a great place to design. But it was never built to produce thousands of variants across formats, languages, and channels. The new GraFx Studio Exporter plugin for Figma bridges that gap – turning a finished Figma frame into a GraFx Studio template, instead of something you rebuild by hand.

The plugin joins the existing exporters for Adobe InDesign and Adobe Photoshop, and runs on Windows and macOS.

---

What Converts

• Text, text styles, and color styles: converted to editable GraFx Studio elements
• Design detail: shapes, images, gradients, drop shadows, opacity, and blend modes are supported
• Preflight: reports what GraFx Studio cannot reproduce exactly, before you export – so you decide, instead of discovering it afterwards

Once imported, the design becomes the master layout for your design system: add variables, rules, and data bindings, then generate on-brand variants across print, digital, and animated output.

---

Experimental Release 0.8.0

This is version 0.8.0 Experimental, available from the plugin downloads page. It is not published on the Figma Community, so you download the ZIP file and add it to Figma as a local plugin yourself. Supported features and behavior can still change between versions.

One tip for a clean conversion: put the design in a single frame, sized as the template should be, and upload the fonts it uses to GraFx Fonts.

Read the Figma plugin guide | Get the plugin

Connector CLI v1.14.0: Compile Errors You Can't Miss, and a Debugger That Stays Out of Your Way

A TypeScript error you don't notice costs more time than the error itself. Connector CLI v1.14.0 puts compile diagnostics where you're already looking, and gives you more control over how the local debug server starts.

---

Compile Errors Appear in the Debugger

When a save introduces a TypeScript error under connector-cli debug, the CLI still logs the diagnostics in the terminal – but now also shows them as a full-page overlay in the debugger. A successful rebuild clears the overlay and reloads the browser tab with the new build. Until the first successful compile, the connector script isn't available in the browser, so you never test against a build that doesn't exist.

Optional Browser Launch and Host Binding

The debug server prints the debug URL and no longer opens a browser by default. Open the URL yourself, or pass --open:

connector-cli debug --open

Need to test from another device on your network? Bind to a specific host:

connector-cli debug --host 0.0.0.0

A Cleaner Debugger UI

The debugger interface now matches the CHILI GraFx platform design. Settings and method inputs persist across the session, so you don't retype parameters on every reload, and copy, empty, and error states are clearer.

---

One Note for Existing Projects

Node.js 20 is no longer supported. Move to a current Node.js LTS release – the same contract described in the prerequisites.

Connector CLI documentation | Pre-requisites

@chili-publish/connector-cli 1.14.0 on npm | GitHub release v1.14.0

Explore the Developer Center

Connector CLI v1.13.0: Your GraFx Connector No Longer Has to Live in a Single File

Things just got more manageable for our GraFx Connnector developers. Every GraFx Connector used to be a single file. As logic grew – pagination, error handling, data mapping – connector.ts grew with it. Connector CLI v1.13.0 ends that: you can now split connector logic across local .ts modules.

---

Multi-File Connector Projects

connector.ts remains the entry point for your projects. The Connector CLI bundles relative imports into a single out/connector.js for publish, test, and debug – exactly the same contract as before.

Two import types are now allowed:

• Relative or local project .ts files: helpers, types, and utilities such as ./helpers or ../utils/format
• @chili-publish/studio-connectors: types and interfaces for the connector runtime

Any other npm package is rejected at compile time with an actionable error, so you find out immediately rather than after publishing.

---

Watch Mode Covers the Whole Project

connector-cli build -w and connector-cli debug now recompile when any project .ts file changes – not only connector.ts. Under build -w, a failed rebuild logs diagnostics and keeps watching instead of exiting, so a typo no longer drops you out of your edit-and-refresh loop.

---

Adding Helpers to an Existing Project

If your project still has "include": ["connector.ts"] in tsconfig.json, widen it to "include": ["**/*.ts"] with node_modules and out excluded, so your editor sees the new modules. Aligning compilerOptions with a fresh connector-cli new project is optional – existing projects keep working as they do today. New projects already ship with both.

Connector CLI | Project structure | Developer Center

Your Render Count Now Reflects Real Production Only

If your usage figures never quite matched what your teams actually produced, here is why. Previews in GraFx Experience were being counted as production renders. That is now fixed.

---

What Changed

Renders are how CHILI GraFx measures usage against your subscription quota – one render for each output you generate. Previews are not output. They are the images GraFx Experience shows while you set up a project, such as the layout thumbnails you see after selecting layouts.

Two fixes land with this release:

• Previews no longer count as production renders: GraFx Experience now generates layout and template-page previews through dedicated preview endpoints that fall outside render counting.
• Preview activity is no longer reported as Image output: Previews were never a downloadable image, so the output-type breakdown in your renders overview now reflects real production only.

The result is cleaner reporting, easier reconciliation, and usage figures you can forecast against with confidence.

---

One Exception: Project Previews

Previews of a project are generated through the regular output routines, using the Output Settings configured in GraFx Experience – so they count as renders like any other output.

If you would rather keep them off your quota, configure those Output Settings to apply a watermark. Watermarked output is tracked as its own category and is not billed.

Read more about Renders

CHILI GraFx Environment API: Brand Kit Media and Colors Can Now Explain Themselves

"Logo alt" and "Accent 2" make perfect sense to the person who created them. To everyone else opening the Brand Kit six months later, they are a guessing game.

The latest CHILI GraFx Environment API release fixes that. Media and color elements now accept an optional description: a free-text string that says what the element is actually for.

---

A Name Identifies, a Description Guides

{
  "media": [
    {
      "name": "Logo",
      "mediaId": "df9c3576-f9ee-4c0e-bfdd-37e2f69da230",
      "description": "Primary logo, for light backgrounds"
    }
  ],
  "colors": [
    {
      "name": "Accent",
      "type": "cmyk",
      "description": "Accent color, reserved for calls to action"
    }
  ]
}

Two things worth knowing:

• A description belongs to the element, not the theme: You set it on the default theme and every theme of the Brand Kit shares it, so "Primary logo" means the same thing on the master brand and on every sub-brand. Editing a description through a non-default theme returns 400 Bad Request.
• It is optional: Existing Brand Kits keep working unchanged, and elements without a description simply return none.

The Brand Kit endpoints of the Environment API accept and return descriptions.

---

Why This Matters

Descriptions turn a Brand Kit into something readable by both people and machines. Usage rules that previously lived in a PDF brand guideline now travel with the element itself.

That context is also groundwork because a name alone does not tell an AI engine which logo suits a dark background. Descriptions do – and GraFx Genie will soon be able to pick the right media item or color for a given design.

How descriptions fit into a Brand Kit

Read more in the Developer Center

GraFx Studio: Pick One Record, Fill a Whole Design with Data Source Variables

Until now, connecting external data to a design meant one thing: an Output data source, iterated row by row to produce a batch. Perfect for 500 personalized mailers. Wrong for one marketer making one poster.

The new Data source variable closes that gap.

---

Pick a Product, Get a Poster

A Data source variable connects to your data system – a product information management (PIM) system, a customer relationship management (CRM) system, an enterprise resource planning (ERP) system – and presents it as a table the end user selects a row from. The selected row stays selected, and the design reads its columns like any other variable value.

Records arrive in one of two ways: pulled live from a data connector, or pushed in by an integration at runtime. End users browse them as a full table or a simple dropdown.

Note: support for this use case is an opt-in capability, so an existing connector may need a small addition first.

Data source variables | Data Connector Fundamentals

Drive Whole Components from One Record

Component variables can now map straight to the columns of a Data source variable. One record fills an entire component in a single step – a product card taking its name, price, and image from the chosen row. A new Available for mapping toggle keeps internal component variables out of the parent mapping list.

Note: a selected row reaches the design through a component. There is no direct route into a text or image frame. And the batch feature previously called Data source is now consistently called Output data source across the interface – unchanged in behavior.

Brand Kit Sync, Governed Centrally

Environment Settings › General now carries a Brand Kit sync settings card with one toggle: Automatically update templates when Brand Kits change. It is on by default. Switch it off and newly imported Brand Kits no longer sync automatically, and individual templates cannot opt back in. Manual sync is unaffected, and the setting is exposed to integrations through the environment settings endpoint.

---

Improvements

Smart Crop: The Point of Interest now snaps when dragged toward the middle of the Subject Area, with dotted guides shown only when aligned. Previews update while you drag in both GraFx Studio and GraFx Media. The Subject type dropdown is hidden when an environment defines no subject types beyond Default.

Editor and text: Component resize mode is now inheritable (default Scale). The editor loads faster – unused fonts are fetched on demand, with output unchanged. Superscript and subscript follow each font's own size and offset, as announced in July. Adjacent variables no longer force a line-wrap point in view mode. In project mode, the SDK emits an event once an end user finishes resizing, rotating, cropping, or editing text in a frame.

Bug Fixes

• Colors and Brand Kits: The picker shows the correct state after switching CMYK to RGB or HEX, theme colors edited in a template sync back correctly, the sync flag no longer reports a sync that never happened, and Smart Crop data refreshes when a theme change swaps an asset.
• Text frames: The loading indicator returns while content loads, and Allow inline text editing no longer redraws with an overridden maximum height.
• Components and actions: Failing variable rules no longer crash a component, default resize mode is correct, action loops are reliably detected, and resetting a layout animation override returns its duration.
• Output: Strokes on image frames are visible in PDF output, and an invalid image is reported per record instead of failing the whole job.
• Interface: The animation reset block design is corrected.

Use components in a template | How to use Brand Kits in a template | Developer Center

CHILI GraFx Environment API: Sign Out of a GraFx Connector Connection

Wrong account signed in to a DAM? Until now, the only way out was to delete and republish the GraFx Connector – disrupting every other user in the process. The CHILI GraFx Environment API now offers a far cleaner path.

---

Clear Your Own Authorization Session

GraFx Connectors that use OAuth 2.0 Authorization Code authorize each user individually. The first time you open a template that reads from such a connector, you sign in to the external system yourself, and CHILI GraFx keeps that authorization session for you.

A new endpoint ends the calling user's own session:

POST /api/v1/environment/{environment}/connectors/{connectorId}/auth/oauth-authorization-code/logout

The next time that user accesses the GraFx Connector, the sign-in flow runs again. Useful when you need to connect as a different account in the external system, or when a session stops working and you want to re-authorize cleanly.

---

Two Things to Know

• This only affects the user making the call: the session is resolved from the access token, so other users of the same GraFx Connector keep their own sessions. There is no way to sign out on someone else's behalf.
• It requires a user token: any user with access to the environment can call it, but integration (machine-to-machine) tokens are rejected.

---

A small endpoint that removes a disproportionately annoying problem – switching accounts no longer means disrupting everyone else.

Authorization for Connectors

Read more in the Developer Center

Connector CLI v1.12.1: A Local Debugger That Behaves Like Production

The gap between "it works on my machine" and "it works once published" used to be where connector development time disappeared. Connector CLI v1.12.1 – the command-line tool used to develop, configure, and manage CHILI GraFx Connectors – closes that gap in the local debugger.

---

See What Every Method Invocation Actually Does

The debugger now shows an Execution metrics panel alongside the output. For every method you invoke, it reports whether the call succeeded or failed, how long it took, and a record of every outgoing fetch – including the URL and the time each one took. If a method made no external calls, the panel says so explicitly, which is a fast way to confirm a caching or short-circuit path is working as intended.

Errors are now visually distinct from successful responses, and formatted JSON output can be copied to your clipboard in one click.

Pasted Asset IDs Are Cleaned Up Automatically

Testing detail or download usually means running query first and copying an ID out of a JSON result – along with stray quotes and braces that make the method fail. Fields that expect an ID now normalize what you paste, extracting the ID and discarding the surrounding JSON.

Watch Mode Is Always On

Run connector-cli debug and the debugger recompiles connector.ts on save and reloads the browser tab. No flags needed. TypeScript compilation problems are now raised as errors instead of leaving you debugging a stale build.

sleep() Works Locally Too

Connectors that poll an external job or back off after a rate-limit response use the global sleep(ms) helper. It existed in the connector runtime but not the debugger, so await sleep(...) failed locally even though it ran fine once published. The debugger now provides it as well – polling and back-off logic can be tested before deployment.

---

Connector CLI documentation

Explore the Developer Center

GraFx Studio: Convert RGB Colors to CMYK in PDF Output

Templates rarely stay in one color space. A photo pulled straight from a DAM is RGB. A brand color defined for screen is RGB. But the press only understands CMYK. Until now, that gap had to be closed manually. Not anymore.

Convert RGB Colors to CMYK in PDF Output

PDF output settings now support converting RGB colors to CMYK during export. This runs as a complementary step to your existing CMYK conversion, bringing RGB content into your print-ready color space automatically.

Here's how it works:

• Enable it in your PDF output setting: Switch on Convert RGB colors to CMYK colors in the Color management section. The switch becomes available once the intended and target CMYK profiles are set, since RGB colors convert to that same target CMYK profile. See the PDF output settings guide.
• Pick an RGB source profile: RGB colors with an embedded profile convert using that profile automatically. For unmanaged RGB colors, choose the assumed source profile – such as sRGB IEC61966-2.1 or Adobe RGB (1998) – from the dropdown that appears.

For Environment API integrations, postProcessing.colorTransformation now accepts two new properties: convertRGBColors (optional, default false) and intendedRGBIccProfile (required when convertRGBColors is true):

{
  "postProcessing": {
    "colorTransformation": {
      "intendedIccProfile": "ISO Coated v2 (ECI)",
      "destinationIccProfile": "Coated GRACoL 2006 (ISO 12647-2:2004)",
      "convertRGBColors": true,
      "intendedRGBIccProfile": "sRGB IEC61966-2.1"
    }
  }
}

For teams running data-driven, multichannel production, this closes a real gap between screen-ready assets and print-ready output – no manual pre-conversion step required.

Read Color Management in PDF Output | PDF Output Settings | Explore the Developer Center

Upcoming Change in GraFx Studio 1.46.0: Superscript and Subscript Now Follow Your Font

Typography is full of small details that carry big meaning: a trademark symbol, a raised cents in a price, math symbols, etc. Starting with GraFx Studio 1.46.0, those details get more faithful to the fonts you choose.

---

What Is Changing

Many fonts include their own instructions for how superscript and subscript characters should look – their size and how far they sit above or below the baseline. Until now, GraFx Studio ignored those instructions and applied a single fixed style to every font. From 1.46.0, superscript and subscript text follows the settings built into each font, read directly from the font's OS/2 table.

Normal baseline text is unaffected. Your content, fonts, and layout are otherwise unchanged. But because most fonts define these values, layouts that use superscript or subscript will generally see some shift in size or vertical position – anywhere from barely perceptible to clearly visible, depending on the font. In tightly fitted text frames, a small change in width can also nudge surrounding text.

---

How to Check If Your Templates Are Affected

This formatting is common in trademark and registered symbols, footnote markers, ordinal numbers (1st, 2nd), prices with raised cents ($19.99), units of measurement (m2, cm3), and chemical formulas (H2O, CO2). To see the real impact:

1. Identify the templates that use superscript or subscript formatting.
2. Before updating, export each one to PDF or image on your current version and keep the output as a reference.
3. After updating to 1.46.0, export the same templates again.
4. Compare the before and after output and confirm the text still looks acceptable.

Where the result isn't what you want, adjust the font, text size, or surrounding layout on the new version until it meets your needs.

---

Prepare at Your Own Pace

As long as a template hasn't been saved on the new version, you can roll back to an earlier one. Pinning your environment version gives you full control over when this change takes effect – ideal for testing in a staging environment before it reaches production.

Manage environment version

Read more in the docs

Questions? Open a ticket at mysupport.chili-publish.com.

GraFx Brand Kits: One Brand Kit, Multiple Visual Identities

Most brands aren't a single, fixed thing. A sub-brand has a different accent color. A print campaign needs a CMYK palette. A regional market calls for its own visual tone. Until now, managing those variations meant duplicating Brand Kits or working around the system. GraFx Brand Kits now solves this with themes.

---

Brand Kit Themes

A Brand Kit can now carry multiple variations of your visual identity through themes. Every Brand Kit has a default theme containing the complete set of elements. Additional themes inherit everything from the default and override only what differs – a sub-brand accent color, a print palette in CMYK, or any other targeted variation.

Themes work across three touchpoints:

• Manage themes in GraFx Brand Kits: Create, rename, and delete themes from the new theme bar on the Brand Kit detail page. Manage themes
• Switch themes in GraFx Studio (Studio + Engine 1.45): The Brand Kit panel's new theme selector updates every Brand Kit element used in the layout, and sync is theme-aware. Switch themes
• Switch themes programmatically: New Actions helper functions getActiveThemeName() and switchTheme(name), or the equivalent Studio SDK methods, let you drive theme switching from automation logic. Switch themes with Actions or the SDK

For teams managing multiple brands, regional variants, or channel-specific palettes from a single design system, this removes a significant layer of duplication.

Read the Themes concept | Explore typical use cases

---

GraFx Studio Improvements (Studio + Engine 1.45)

This release also includes a set of GraFx Studio refinements:

• Heavy media assets no longer fail prematurely: Studio now waits up to 10 minutes for GraFx Media to process an asset before giving up.
• Font previews: An additional fallback ensures previews render in more cases.
• Undo and redo in text editing behave more predictably.
• Subject type fallback on asset details: When a custom subject type has no settings of its own, the default subject type settings are now applied.
• Long layout and variable names are easier to read in their panels.

---

Bug Fixes

• Fixed canvas rendering in the space between the left panels.
• Fixed text selection in input fields using various mouse clicks.
• Fixed validation in particular input fields.
• Fixed text going into overflow with copyfitting and auto-grow enabled on multicolumn frames.
• Improved PDF generation performance.

CHILI GraFx Environment API: Big Templates Fully Reliable

A project built on a large, complex design shouldn't fail just because the underlying document is big. Yet some output requests for large documents were returning 413 Content Too Large errors, even when the actual variable data behind them was small.

That's fixed now.

What Changed

The 10 MB size limit on output requests previously applied to the entire request body – including documentContent, which grows naturally with template complexity. Now, that limit applies only to the variables property, not the request as a whole. Large templates with rich documentContent no longer get penalized for size that has nothing to do with the data being merged in.

Why It Matters

If you generate output from projects built on big templates – think dense catalogs, multi-page layouts, or asset-heavy designs – you can now request output without hitting artificial size errors tied to document complexity rather than actual variable data volume.

Full details, including the separate 20 MB hard limit on total request size, are covered in the Output API limitations.

Read more in the Developer Center

CHILI GraFx Environment API: Take Control of Headers in GraFx Connector Proxy Requests

Some external systems hand back pre-signed URLs – CDN links that carry their own authentication in the query string. When the CHILI GraFx proxy forwards your GraFx Connector's Authorization header to one of those URLs, the upstream rejects the request and the asset fails to load. It's a subtle conflict between two valid authentication mechanisms, and until now there was no clean way to resolve it.

The CHILI GraFx Environment API now gives you that control.

---

Exclude Specific Headers on a Per-Request Basis

A new request header – X-GraFx-Proxy-Exclude-Headers – lets you tell the proxy exactly which headers to drop before the outbound request reaches the external system. Provide a comma-separated list of header names, and those headers are removed. Header names are matched case-insensitively, surrounding whitespace is trimmed, and X-GraFx-Proxy-Exclude-Headers itself is never forwarded.

For example, to prevent the connector's Authorization header from reaching a pre-signed CDN URL:

X-GraFx-Proxy-Exclude-Headers: Authorization

This works on both GET and POST connector proxy requests.

---

Practical Impact

This update directly fixes a reliability issue for GraFx Connectors that serve assets through time-limited signed URLs – including the Aprimo connector. Those connectors can now work without the proxy interfering with the upstream's own authentication mechanism.

For teams building headless production workflows on CHILI GraFx, this is a targeted fix that removes an edge-case failure point without requiring any changes to existing connector configuration.

Read more in the Developer Center

GraFx Studio: Smarter Smart Crop, Combined Text Sizing, and More

AI-powered image cropping is only as good as its predictability. When a designer can't trust that the subject will land where it should across every aspect ratio, they end up babysitting automation instead of benefiting from it. This GraFx Studio release addresses that directly – with a major upgrade to Smart Crop and a set of improvements that make building design systems faster and more reliable.

---

A Smarter Smart Crop

Smart Crop is GraFx Studio's AI-driven fill mode, powered by GraFx Genie, that automatically positions an image inside a frame so the most important part stays visible. This release is a significant step forward.

The updated algorithm is built around clear priorities: the frame is always filled completely, the Point of Interest always stays inside the Subject Position, and as much of the Subject Area as possible is preserved – cropping only as a last resort. Less trial-and-error, more consistent results.

Four additional improvements come with this upgrade:

• Subject alignment: Nudge the subject toward any side of the Subject Position instead of always centering it – useful when a subject needs to sit against a layout edge across different aspect ratios.
• Automatic versioning: Each frame keeps the Smart Crop version it was built with, so existing designs render exactly as before. A "New smart crop available – apply it" prompt lets you upgrade any frame to the latest algorithm in one click.
• Five live previews: The asset details panel now shows five preview aspect ratios instead of three, in both GraFx Media and the GraFx Studio workspace, making it easier to validate Subject Area and POI settings before committing.

Read the full Smart Crop guide

---

Auto-Grow and Copyfitting Together

Text frames can now use auto-grow and copyfitting at the same time. A frame can expand to fit its content while copyfitting keeps the text within defined size limits – a combination that previously required choosing one behavior or the other. For data-driven layouts with variable text lengths, this removes a real design compromise.

---

More Improvements in This Release

• Component image variables mapped to list variables: Template Designers can now map a component's image variable to a single-select list variable, giving more flexibility in how component imagery is driven from list-based choices.
• Richer metadata mappings: Metadata mappings now support additional variable types, so more asset metadata can flow into layouts automatically.
• Layouts & Pages tabs always visible: The Layouts and Pages tabs now stay visible for every layout intent – including animation and digital static – keeping navigation consistent regardless of what you're designing.
• Reorganized gradient color picker: The Colors/Custom toggle now sits below the gradient bar for a cleaner, easier-to-read interface.
• Clearer missing font warning: When you add a component containing a missing font, GraFx Studio now shows an error dialog immediately instead of failing silently.
• GraFx Connector improvements: Unused GraFx Connectors are automatically removed from a document on save, and connector mapping now offers expanded options for how a data source maps into your layouts.

---

Bug Fixes

This release also resolves several issues across the workspace: the Layouts panel no longer jumps to the top when selecting a layout; the override dropdown is correctly sized again; the interface refreshes properly when undoing a variable switch; a template keeps its correct name after "Save as"; and the character-limit field accepts its maximum value again.

On the text rendering side, three issues are fixed: incorrect letter tracking when combined with a stroke, a misplaced glyph for a specific font, and a separate font that rendered incorrectly.

For images and frames: canvas images now update immediately after a GraFx Brand Kits sync, and copying and pasting an anchored frame onto a different page works correctly.

For reliability: all requests now go through the authentication refresh mechanism – reducing unexpected failures during long sessions – and the SDK's image-upload staging call handles token expiration correctly.

---

Check out GraFx Studio to explore everything in this release.

CHILI GraFx Environment API: Font Previews Now Display Correctly for Newly Uploaded Fonts

A font preview is the sample image CHILI GraFx generates for each font style – a quick visual reference so you can identify a typeface at a glance without opening a design. When those previews render incorrectly, choosing the right font becomes a guessing game.

This fix puts that right.

Square Font Previews Now Wrap Correctly

The 400×400 square preview generated for newly uploaded fonts was rendering its sample text on a single line, leaving most of the preview area empty instead of showing a properly wrapped, readable sample. Newly uploaded fonts now generate a correctly wrapped square preview – showing the typeface as intended.

No configuration changes are needed. The corrected behavior applies automatically to fonts uploaded going forward.

For teams managing large font libraries through GraFx Fonts, accurate previews are a small but meaningful part of keeping designers moving quickly – the right typeface, confirmed at a glance.

Read more in the Developer Center

CHILI GraFx Platform: Faster Integration Testing, Smarter Asset Management, and Cleaner Connector Visibility

A handful of well-placed improvements can quietly remove a lot of daily friction. This CHILI GraFx platform update does exactly that – across integration setup, asset management in GraFx Brand Kits, GraFx Studio library navigation, and GraFx Connector configuration.

---

Generate an API Token in One Click

Testing an integration against the GraFx APIs used to mean running through the full OAuth flow just to get a token. That step is gone. You can now generate a token directly from the integration settings panel – right next to the client secret – and copy it to the clipboard in a single click. A toast confirms the copy. No extra tooling required.

---

Sort Templates and Elements by Date in GraFx Studio

The Templates and Components pages in GraFx Studio now support two additional sort options: Date created and Last modified. Both appear as columns in the list view, with times displayed in UTC for consistency. In larger libraries, this makes it straightforward to surface recently updated designs without scrolling through everything else.

---

Clearer Visibility for GraFx Connector CLI Installs

GraFx Connectors deployed via Connector CLI are now shown in a disabled state on the environment's Connectors page. The availability toggle is visible but no edit actions are available – hovering over the row shows a tooltip explaining that editing must happen through Connector CLI. The Add Connector button now goes directly to the Connector Hub flow, without an intermediate modal.

Separate Authentication for Single-Auth GraFx Connectors

GraFx Connectors that expose only one authentication method can now have separate authentication configuration for server-side and browser-side use. This is particularly useful for token injection scenarios – for example, setting browser authentication to [None] while the server uses a configured auth method. Previously, this flexibility was only available for GraFx Connectors supporting multiple auth methods.

---

More Control Over Assets in GraFx Brand Kits

Two improvements make Brand Kit asset management more flexible:

• Broken references: If a media asset used in a Brand Kit has since been deleted from GraFx Media, the Brand Kit now shows a clear "Image not available" placeholder with Replace image and Delete image actions to resolve it.
• Universal replace: The Replace image action is now available for all assets in a Brand Kit – not just deleted ones – so you can swap out any image without removing and re-adding it.

---

Bug Fixes

• Pressing Enter in description input fields (such as integration descriptions or GraFx Connector JWT private key fields) now correctly adds a new paragraph in all cases.
• The storage indicator on the CHILI GraFx homepage now correctly reflects used and total storage across all subscription configurations.

CHILI GraFx Environment API: Clearer Swagger Examples and Faster Responses

Good API documentation and fast response times are not optional extras – they are the foundation that integrations are built on. The latest CHILI GraFx Environment API update delivers on both.

---

Swagger Examples That Reflect Reality

The Swagger examples for the Media and Template GET endpoints have been refreshed to accurately reflect what the API returns today. When the examples in your interactive documentation match actual responses, building and debugging integrations becomes significantly faster – no more cross-referencing what the docs say with what the API actually returns.

You can access your environment's Swagger documentation directly from your integration setup. See Making API Calls for details.

Faster Responses on the Operations You Use Most

The most heavily used Environment API operations now respond faster, thanks to more efficient cache communication. No changes are needed on your side – the improvement is automatic.

For teams running high-volume, data-driven content production on CHILI GraFx, faster API responses compound quickly across automated workflows.

---

Read more in the Developer Center

Adobe® Photoshop® Clipping Masks Now Export to GraFx Studio

Moving a Photoshop® document into another system rarely goes without a hitch. Shaped images lose their masks, arrive as plain rectangles, and need to be rebuilt by hand. With v1.4.0 of the GraFx Studio Exporter for Adobe® Photoshop®, that rebuild step is gone.

Clipping masks – one of the most common image shaping techniques in Photoshop® – are now preserved when you export to GraFx Studio.

---

Clipping Masks That Arrive Intact

The exporter translates Photoshop® clipping setups into Studio-native clipping masks, covering two scenarios:

• Built-in shapes: Images clipped with a Rectangle, Ellipse, or Polygon export as Studio clipping shapes, with corner and stroke properties preserved.
• Custom paths: Images clipped with a custom path are converted to a path-based clipping mask in GraFx Studio.

Stroke color, stroke width, and corner properties all carry through. Nothing needs to be reconfigured after export.

---

A Note on Preflight Warnings

The exporter shows a preflight warning for every document that contains at least one clipping mask. This is a precaution: in Photoshop®, a clipping mask can extend beyond the image it clips and display an overflow fill – something GraFx Studio handles differently. If your masks stay within their frames, the warning can safely be ignored.

Merged shapes, combined shapes, masks applied to layer groups, and complex paths are not yet supported and will be flagged in preflight.

---

For teams converting Photoshop® layouts into scalable GraFx Studio design systems, this update removes a meaningful manual step. The visual structure you built in Photoshop® arrives ready to use.

Read the GraFx Studio Exporter for Adobe® Photoshop® documentation

TIFF Images Now Supported in Print Output via GraFx Media

Print production has always demanded color accuracy above everything else. When a CMYK image loses its color space somewhere between the asset library and the final PDF, the consequences show up on press – and fixing them costs time, money, and trust. GraFx Media now closes that gap for TIFF assets.

TIFF images stored in GraFx Media can now be used in your designs and will come through correctly in PDF output generated by GraFx Studio.

---

Full Resolution, Original Color Space – All the Way to Print

When GraFx Studio generates a PDF for print, TIFF assets are now served at full resolution with their original color space intact. A CMYK TIFF stays CMYK from GraFx Media through to the final PDF. No color space conversion, no quality loss, no surprises at the print stage.

This matters most for teams producing print-ready output at scale – packaging, catalogues, direct mail, point-of-sale materials – where color fidelity is a hard requirement, not a preference.

---

TIFF Joins the Full Print Format Lineup

TIFF now works alongside JPG, PNG, and PDF as a supported format for high-resolution print output in GraFx Media. For production teams whose asset libraries are built around TIFF files – a common standard in professional photography and prepress workflows – this removes a real barrier.

Previously, using a TIFF asset meant converting it to another format before it could be placed in a design destined for print. That extra step added friction to the workflow and introduced the risk of color profile changes during conversion. Now, TIFF assets can go straight from GraFx Media into a print-ready PDF without any intermediate processing.

---

What This Means in Practice

For designers and production teams working inside CHILI GraFx:

• TIFF assets already stored in GraFx Media are ready to use in print layouts without any reformatting.
• Color accuracy is preserved end to end – the asset that goes in is the asset that comes out in the PDF.
• Workflows that rely on data-driven or automated print output benefit immediately, since TIFF assets can now participate in batch PDF generation alongside other supported formats.

This update aligns GraFx Media with the supported formats defined for the media connector, keeping the platform consistent for teams building on the CHILI GraFx API-first architecture.

---

For print-focused production workflows, reliable color handling is foundational. TIFF support in GraFx Media print output means one fewer conversion step, one fewer point of failure, and more confidence that what you design is exactly what gets produced.

Read more in the Developer Center

CHILI GraFx Environment API: Know Which Apps Are Enabled and Handle Expired Outputs Gracefully

Two small API updates. Two real improvements to how integrations behave in production. The latest CHILI GraFx Environment API release adds visibility into per-environment application availability and fixes a frustrating gap in how expired output downloads are reported.

---

Per-Environment Application Settings

CHILI GraFx environments are isolated workspaces – each one can have its own configuration, its own users, and its own set of active applications. Until now, the Environment API settings endpoint didn't tell you which applications were actually enabled for a given environment. You had to know that separately, outside the API response.

That changes with this update. The settings endpoint now returns which CHILI GraFx applications are enabled for an environment. This is the first step toward configuring application availability per environment through the API – and for integrators building on top of CHILI GraFx, it means one less assumption baked into your integration logic.

If you're building a portal or a headless production workflow that spans multiple environments, this gives you a reliable, programmatic way to understand what's available where – before you try to use it.

Read the version and settings documentation

---

Clearer Response When Downloading an Expired Output

Output files generated through the CHILI GraFx API don't live forever. Tasks remain available for 7 days, but the download window for the generated file is 4 hours. After that, the file is cleared from temporary storage.

Previously, requesting a download after that window had closed returned a generic server error. For integrations polling output status or triggering downloads asynchronously, that response was indistinguishable from a genuine failure – a crashed job, a server problem, something that needed investigation.

Now, requesting an expired output returns a clear "no longer available" response. The distinction matters: an integration can reliably tell an expired output apart from a real failure and react accordingly – for example, by regenerating the output rather than filing a support ticket.

This is a small fix with a meaningful impact on how automated workflows handle edge cases in production.

Output Tasks – Availability

---

For teams running data-driven, high-volume content production on CHILI GraFx, predictable API behavior is not a nice-to-have – it's the foundation that everything else depends on. These updates make two parts of that foundation more reliable.

Explore the full documentation in the Developer Center

CHILI GraFx Environment API: Your Print PDFs Now Get the Full-Quality Source Image

Color fidelity in print is unforgiving. A CMYK image that quietly converts to RGB somewhere in the output pipeline doesn't announce itself – it just arrives at the press wrong. For teams producing print-ready PDFs through the CHILI GraFx Environment API, that kind of silent quality loss is exactly the problem this fix addresses.

The Environment API now returns the original source file for JPG and PNG assets when GraFx Studio generates a PDF. The image's original color space and quality carry through to the final output, intact.

---

What Changed – and Why It Matters

When GraFx Studio generates a PDF, the output engine requests each placed image at full resolution for print. Previously, JPG and PNG assets were not always served as their original source files during this process. That meant the color space of the image – including CMYK values carefully set by a designer or production team – could be altered before it ever reached the PDF.

The fix is direct: the Environment API now returns the original source file for JPG and PNG assets on print output requests. A CMYK JPEG stays CMYK all the way through to the final PDF. No silent conversion, no unexpected color shift, no manual correction step after the fact.

This behavior is documented in the media connector fundamentals for supported formats.

---

Who This Affects

This fix is relevant for any team using the CHILI GraFx Environment API to generate print PDFs from GraFx Studio designs that include JPG or PNG assets – particularly where those assets carry CMYK color data.

For production workflows where color accuracy is non-negotiable – retail packaging, brand campaigns, regulated print materials – this closes a gap between what the design system specifies and what the output delivers. The image you placed is the image that prints.

No configuration changes are needed. The corrected behavior applies automatically to print output requests going forward.

---

For teams building headless production pipelines on top of the CHILI GraFx API-first architecture, predictable output behavior is foundational. A fix like this reinforces that what you put into the system is what comes out – at full quality, with the color profile you intended.

Read more in the Developer Center

Preview Every Layout Before You Personalize with CHILI GraFx Environment API

When a design system holds a dozen layout variants – social ads, print formats, animated banners – showing end users a single thumbnail and asking them to guess the rest is a poor experience. It slows decisions, increases errors, and puts unnecessary friction between a user and the output they actually need.

The CHILI GraFx Environment API now removes that friction entirely.

---

Per-Layout and Per-Page Preview Thumbnails

A GraFx Studio design can contain multiple layouts – variants of the same design at different sizes or for different channels – and each layout can have multiple pages. Until now, the template preview endpoint always returned the preview of the default layout and default page only.

That limitation is gone. You can now request a preview for any specific layout and page combination within a multi-layout design. This unlocks per-layout and per-page thumbnail generation for downstream applications, including GraFx Experience.

---

What This Means for Integrators and End Users

For integrators and ISVs building portals on top of CHILI GraFx, this opens up a more complete self-serve experience. A design system delivered as a single multi-layout design holds all the variants of a campaign – different sizes, channels, or page sequences – in one place.

Instead of surfacing a single thumbnail, a portal can now render a thumbnail for every variant the design system contains. End users can visually compare each layout and page before choosing the one they want to personalize or export. That is a meaningful step toward truly self-serve content production at scale.

---

The API Change

Two existing endpoints now accept two new optional query parameters – layoutId and pageId:

GET /api/v1/environment/{environment}/templates/{templateId}/preview
GET /api/v1/environment/{environment}/templates/{templateId}/preview/{previewType}

Key behaviors to know:

• Backwards-compatible: when both parameters are omitted, the endpoint returns the default layout and default page preview exactly as before.
• When either parameter is provided, the preview is rendered – or served from cache – for that specific layout and page combination.
• When either parameter is provided but the rendering engine version is below 2.24.0, the endpoint returns 400 Bad Request with a message indicating the minimum supported engine version.

No breaking changes. Existing integrations continue to work without modification.

---

For teams building on the CHILI GraFx API-first architecture, this update closes a real gap in the headless production experience. Design systems are built to scale across channels and formats – now the preview layer keeps pace with that ambition.

Explore the full documentation in the Developer Center

Adobe® InDesign® Clipping Masks Now Export to GraFx Studio

Every designer who has moved a document from Adobe® InDesign® into another system knows the feeling: something always gets lost in translation. A carefully shaped image frame arrives as a plain rectangle. Hours of visual work need to be rebuilt from scratch. With v1.4.0 of the GraFx Studio Exporter for Adobe® InDesign®, that particular frustration is gone.

Clipping masks – one of the most common image shaping techniques in InDesign® – are now preserved when you export to GraFx Studio.

---

Clipping Masks That Survive the Export

GraFx Studio recently added native clipping mask support for image frames, letting designers assign rectangle, ellipse, or polygon shapes to control how an image is displayed. The InDesign® plugin now closes the loop on the import side: the shapes you've already built in InDesign® come through intact.

The exporter handles three distinct clipping scenarios:

• Built-in shapes: Image frames clipped with a rectangle or ellipse are exported as Studio-native clipping shapes, with corner-radius and stroke properties preserved.
• Custom paths: Frames clipped with a custom path are converted to a path-based clipping mask in GraFx Studio, with the path's stroke carried through.
• Nested shapes containing images: When an image frame is pasted inside a shape, the immediate parent shape becomes the clipping path, and the image's own clipping is applied on top.

Strokes applied to clipped image frames export alongside the mask. Nothing needs to be reconfigured after import.

---

Preflight Keeps You Informed

Not every clipping setup can be translated yet. Complex paths – such as multiple unconnected paths or a path containing another path – are not fully supported in this release. Rather than silently dropping them, the preflight panel flags these setups before export, so you know exactly what to expect and can decide how to handle each case.

The exporter also applies a clear detection rule: a shape that contains an image is treated as a clipping mask. A shape on its own – with no image inside – exports as a standalone shape asset, keeping its geometry without acting as a mask.

---

For teams converting InDesign® layouts into scalable GraFx Studio design systems, this update removes a meaningful manual step. The visual structure you built in InDesign® arrives in GraFx Studio ready to use – shaped, stroked, and production-ready.

Read the GraFx Studio Exporter for Adobe® InDesign® documentation

Highlighted Text, Sharper Kerning, and More – GraFx Studio v1.43

Typography details matter more than most people realize. A headline with uneven letter spacing, or a label that loses its colored highlight when text resizes – these are the small inconsistencies that quietly undermine an otherwise polished design. GraFx Studio v1.43 addresses both, along with a set of other improvements that make layouts more precise and end users more self-sufficient.

---

Background Color on Character Styles – Highlights That Scale With Your Text

Character styles in GraFx Studio now support a background color – the colored fill that sits behind a word or phrase, like a marker effect. It's the right tool for callouts, badges, labels, and short emphasized runs of text inside a paragraph.

Enable it in the character style editor and pick any color from your Brand Kit – gradients are supported. Once set, every text selection using that style picks up the background automatically. And when text resizes to fit its frame, the highlight resizes with it. No misalignment, no manual adjustment.

How to work with character styles

---

Kerning Pairs – Text That Looks the Way Your Font Was Designed

Professional fonts include built-in spacing adjustments between specific letter combinations – pairs like "AV", "JA", or "Te" – defined by the type designer to keep the visual rhythm of a line consistent. Until now, GraFx Studio didn't apply these automatically.

v1.43 changes that. Kerning pairs are now picked up during text layout with no extra setup required. The result is text rendering that aligns closely with what you'd see in InDesign or Illustrator – which matters especially when designs move between tools or when typographic precision is part of the brand standard.

---

More Options for Image Clipping Masks

The clipping mask feature introduced in v1.42 lets you crop an image into a rectangle, ellipse, or polygon. v1.43 adds a fourth option: a Custom shape. An image can now be clipped into any silhouette you bring in – including shapes exported from InDesign – giving layouts more creative range when an unusual cut-out is part of the design.

Clipping mask on image frames

---

Clearer Feedback When Text Exceeds Its Limit

When an end user enters text longer than a variable allows, GraFx Studio now shows a plain-language message explaining what's wrong and how to fix it. This is especially useful in the Studio UI, where users are filling in layouts on their own and need immediate, actionable guidance rather than a silent failure.

---

Also fixed in this release:

• Text inside Components renders crisply – text inside a Component now displays at the same sharpness as text anywhere else on the canvas.
• Animations in Components stay consistent – animations on frames inside a Component now play the same way in both preview and final output.
• Image variable settings preserved across mapping edits – browse options and hardcoded values are kept when you adjust metadata mappings.
• Aspect ratio checks restored in preflight – preflight once again flags frames whose content breaks aspect ratio rules.
• Large image variable uploads complete reliably – high-resolution TIFFs around 70–100 MB now upload successfully.

---

From typographic precision to self-serve error guidance, v1.43 tightens the details that keep design systems accurate and production workflows running without interruption.

Image Clipping Masks & Ways to Guard Your Copy

Two of the most common friction points in high-volume content production are visual: an image that needs a non-rectangular shape without a workaround, and text that breaks a layout because someone typed too much. CHILI GraFx v1.42 addresses both directly.

---

Clipping Masks for Image Frames – Circles, Rounded Cards, and More

Until now, getting a circular avatar or a rounded product card meant placing a separate shape frame on top of an image frame and managing both. That workaround is gone.

Image frames in GraFx Studio now have a built-in Clipping mask section in the property panel. Assign a rectangle, ellipse, or polygon to define the visible silhouette of the image – and add a corner radius to soften edges or create fully rounded shapes.

What makes this especially useful for production work:

• Stroke and drop shadow follow the clipped path exactly. There is no misalignment between the visual shape and its outline or shadow – the effect is always precise.
• Existing layouts are unaffected. Every image frame defaults to a rectangle without a stroke, so nothing changes unless you actively configure it.
• It works within the frame's existing dimensions. The clipping shape fits inside the frame's bounding box – no repositioning required.

This is a direct time-saver for design systems that include circular profile images, badge-style product visuals, or any layout where image shape is part of the brand.

Clipping mask on image frames

---

Character Limits for Text Variables – Governed Copy at Every Step

When end users fill in layouts, text length is one of the hardest things to govern. A headline that runs too long breaks the design. A product description that overflows a frame creates output that needs manual correction.

GraFx Studio v1.42 adds maximum length enforcement to both single-line and multi-line text variables. Set the limit once in the variable settings, and it applies everywhere that variable can be edited.

• A remaining-characters counter appears on the input field, so users always know where they stand.
• Typing is blocked once the limit is reached – no silent overflow.
• Pasted text is truncated to fit, rather than rejected entirely.
• The same limit applies when values come in from a data source, keeping automated and manual workflows consistent.

This gives designers precise control over copy length without relying on end users to self-regulate – and it keeps layouts intact across every output.

Single-line text variables – maximum length · Multi-line text variables – maximum length

---

Also fixed in this release:

• Clearer output failure messages – animated layouts that excluded a failing page previously reported Internal error. Failures now report as Failed with a meaningful message.
• Component sizing after layout switches – Flutter-based outputs could render elements at the wrong size after switching between layouts of different dimensions. Elements now stay in sync with the active layout.

---

Clipping masks and character limits each solve a specific production problem – one visual, one editorial. Together, they extend the precision that GraFx Studio design systems can enforce, from how images look to how copy behaves, across every layout and every output.

Connector CLI update: Cleaner Auth Management and More

Reconfiguring a Connector's authentication shouldn't mean tearing it down and starting over. Until now, that was exactly the situation developers faced when they needed to remove or switch an authorization type on a CHILI GraFx Connector. Connector CLI v1.12.0 fixes that – and brings a set of reliability improvements that make connector development more predictable from setup through production.

---

Remove Connector Authentication Without Rebuilding

Connectors in CHILI GraFx authenticate against external systems using one of five supported authorization types – from Static Header Key to various OAuth 2.0 variants – configured via the set-auth command.

The problem: once that configuration was in place, removing it entirely meant deleting and re-creating the Connector from scratch.

v1.12.0 introduces delete-auth, a new command that removes a Connector's authorization configuration cleanly:

connector-cli delete-auth

Switch auth types, revert to no authentication, or clear a configuration that's no longer needed – without touching the connector itself.

Change/Remove Configured Authentication

---

Catch Auth Errors Before They Happen

Previously, running set-auth with an incomplete authorization data file would appear to succeed – only to fail later when the Connector first tried to authenticate. That delayed feedback made debugging harder than it needed to be.

The CLI now validates that all fields required by your chosen authorization type are present in the data file at the time you run set-auth. Missing or incomplete fields are flagged immediately with a clear error, so you fix the configuration before it ever reaches runtime.

---

Connector Responses Always Reflect Current Data

Connectors that return frequently-changing data – asset listings, metadata, search results – were sometimes serving stale responses due to unexpected caching behavior.

Connector responses now include an explicit Cache-Control: no-cache header. Data fetched through a connector always reflects the current state of the source system, which is especially important for connectors powering dynamic, data-driven output at scale.

---

More Predictable Response Content Types

Connector responses now align consistently with their declared content type. For developers building integrations against the GraFx Connector framework, this means downstream parsing is more reliable – fewer edge cases, less defensive code, and more confidence that the data arriving matches what was declared.

---

These improvements reflect a clear direction for the Connector CLI: less friction when configuring connectors, and more confidence that what you build behaves correctly in production. Whether you're developing a custom connector for a DAM, a PIM, or any other MarTech system, v1.12.0 makes the tooling more dependable at every stage.

Explore the full Connector documentation in the Developer Center

Smarter Crops, Always-Fresh Brand Kits, and More – GraFx Studio v1.41

When the same product image needs to look right as a hero shot, a thumbnail, and a print ad – all cropped differently, all on-brand – the gap between intent and output can quietly eat hours of production time. GraFx Studio v1.41 closes several of those gaps at once.

---

Subject Types for Smart Crop – One Asset, Multiple Crop Intents

Smart Crop, powered by GraFx Genie, already automates how images are cropped to fit a frame. v1.41 adds a new layer of precision: subject types.

A subject type is a classification you assign to an asset – for example, person, product, or logo – that tells GraFx Studio what kind of subject the image contains. When Smart Crop is active on a frame, selecting a subject type directs the crop to use the Subject Area and Point of Interest stored for that specific type.

The practical result: the same source image can be cropped differently depending on context. A lifestyle photo might crop to the person for a social ad and to the product for a catalog page – without duplicating the asset or rebuilding the frame.

Subject types are also visible in the media details view alongside the asset's other metadata, so the classification travels with the asset wherever it's used.

• Smart Crop subject types – concept
• Select a subject type on a frame
• Set a Subject Area per subject type

---

Central Subject Type Management in the Platform

Subject types are managed centrally in CHILI GraFx, not scattered across individual templates. A dedicated Subject types page in environment settings lets admins define and maintain the full list available across their environment.

This means designers and end users always pick from a governed, consistent set of classifications – and any update made centrally is immediately reflected everywhere the types are used.

• Manage Subject Types

---

Brand Kit Sync – Stay Aligned Without Re-importing

Brand Kits define the visual foundation of every design: colors, fonts, styles, media. But until now, keeping a layout aligned with an updated Brand Kit meant re-importing it manually – a friction point that slowed down teams managing active brand identities.

v1.41 removes that friction. Brand Kits in GraFx Studio can now stay in sync with their source.

• Auto-sync: When enabled, GraFx Studio checks the source Brand Kit every time a template is opened or the Brand Kit panel is accessed, and applies any changes automatically. A confirmation message lets you know when a sync has run.
• Manual sync: A single button pulls the latest Brand Kit version on demand – useful when you want to control exactly when an update lands.

Newly imported Brand Kits have auto-sync enabled by default. Either way, layouts stay aligned with the latest brand definitions without rebuilding from scratch.

• Keep a Brand Kit in sync

---

Clearer Feedback on Autogrow Interactions

When autogrow is active on a text frame, certain interactions – constraining proportions, applying rotation – aren't available on those layouts. Previously, this wasn't surfaced clearly, which could leave designers wondering why a control wasn't responding.

v1.41 adds two targeted info messages that explain exactly what's happening and why, so you spend less time troubleshooting and more time building.

• Auto-grow on text frames

---

Also fixed in this release:

• PDF overprint preserved – embedding PDF assets with overprint statements no longer strips overprint from the final PDF output.
• Image variable metadata mappings – mappings on image variables can now be updated after being set for the first time.

---

Subject types, Brand Kit sync, and clearer autogrow feedback each address a specific point where production slows down. Together, they reflect a consistent direction for GraFx Studio: more predictable output, less manual correction, and design systems that stay accurate as brands evolve.

Your CSV File Is Now a Live Data Source in GraFx Studio

Most teams already have their data in a spreadsheet or CSV file/export. Product names, prices, campaign copy, regional variations – it's all there, sitting in a file. The gap has always been getting that data into a design without rebuilding it row by row.

GraFx Studio now closes that gap with the new CSV Data Connector.

---

Connect a CSV File in Seconds

The setup is straightforward. Paste the public URL of your CSV file into the connector configuration, and GraFx Studio takes it from there – reading the column headers and mapping them to your layout variables automatically.

No authentication required. No manual field mapping. If your file is publicly reachable, the connector can use it.

Each row in the file becomes a record. Each column becomes a variable bound to your layout. Browse through records in Run Mode or the Studio UI to preview exactly how your design looks with each row of data before generating output.

---

Built to Handle Real-World Data

CSV files come in many shapes. The connector handles the most common variations without any extra configuration:

• Comma and semicolon delimiters – detected automatically from the first line of the file.
• Quoted fields – fields containing commas, semicolons, or line breaks are fully supported.
• Excel UTF-8 exports – the UTF-8 BOM added by Excel's "Save as CSV UTF-8" is stripped automatically.
• Automatic type inference – the connector samples each column and assigns the right variable type: text, number, date, or boolean. You don't configure anything; it figures it out.

Leading zeros are preserved as text, so product codes and postal codes stay intact.

---

From One Record to Thousands

Once your CSV is connected, generating output at scale is a single step. Enable the Data source option in your output settings, and GraFx Studio produces one page per record in the file. A product catalog with 500 SKUs becomes 500 personalized outputs – driven entirely by the data in your CSV.

You can also deploy multiple instances of the connector, each pointing to a different file. One instance for a product feed, another for a regional campaign list – each layout draws from the source that fits.

---

One Hosting Note

The CSV file must be served with a Content-Type: application/json response header. The file content itself is unaffected – only the header matters. Any static host where you can set response headers works: AWS S3, Azure Blob Storage, or a CDN.

---

The CSV Data Connector is the fastest path from a data file to data-driven output in GraFx Studio. If your team already works with spreadsheets and CSV exports, your data is ready to power scalable content creation – today.

Read the CSV Data Connector documentation

Your Bynder DAM Is Now Connected to GraFx Studio

Every team that runs a Digital Asset Management (DAM) system knows the friction: the right asset is in the DAM, but getting it into a design means downloading, re-uploading, and hoping nothing is out of date by the time output runs. For teams using Bynder, that friction is now gone.

The Bynder media connector is now available in the Connector Hub – and once installed, your GraFx Studio designs can browse and use Bynder assets directly, without a single manual upload.

---

What the Bynder Connector Does

The connector brings your Bynder DAM into GraFx Studio as a live media source. Assets are accessible in two ways:

• Directly on the canvas – browse and place Bynder assets into image frames while building or editing a design.
• Through image variables – assign Bynder assets to image variables, enabling data-driven and self-serve workflows where end users select from a governed set of approved assets.

Both paths give your team access to brand-managed content right where the work happens – no context switching, no duplicate files.

---

Built for Governed, Scalable Content Production

The connector is designed to support the kind of structured, high-volume content production that CHILI GraFx is built for.

OAuth 2.0 authentication keeps access secure and aligned with how your Bynder environment is already governed. Your team works with the assets they are entitled to – digital rights from Bynder carry through into GraFx Studio.

Metadata mapping means the information attached to a Bynder asset – product names, campaign tags, descriptors – can be mapped to variables inside your design. When an end user selects a different asset, the metadata updates accordingly. This is the foundation for truly data-driven output: the right image and the right information, together, automatically.

Collection and folder view filtering lets you control which assets are surfaced to end users. Instead of presenting an entire DAM library, you can scope the selection to a specific collection or folder – so users only see what is relevant to the design they are working on.

---

Getting Started

Installation is straightforward. The Bynder connector is available in the Connector Hub – navigate to your environment settings, select Connectors, and add it from the Hub. Configuration requires your Bynder base URL and OAuth 2.0 credentials, which your Bynder administrator can provide.

Once active, the connector appears as a media source in GraFx Studio, ready to use across any design in that environment.

---

For teams already invested in Bynder as their source of truth for brand assets, this connector closes the loop between asset management and content production. Your DAM investment works harder. Your designers work faster. And every output starts from an approved, up-to-date asset – by default.

Read the Bynder Connector documentation

More Faithful Rendering of Your InDesign and Photoshop Designs in GraFx Studio – Plugin v1.3.0

Every designer who has moved a document from Adobe InDesign or Photoshop into another system knows the feeling: something always gets lost. A text column collapses. A bulleted list flattens. A locked layer disappears entirely. The gap between your original design and what arrives on the other side costs time – and erodes confidence in the conversion process.

Plugin v1.3.0 for GraFx Studio closes that gap.

---

Adobe InDesign Plugin – What's New

This release adds support for some of the most common InDesign layout structures that previously required manual workarounds after import.

Text columns

Text frames with multiple columns now export with their column structure intact. If your layout relies on multi-column text flow, that structure carries through to GraFx Studio without rebuilding.

Bullet and numbered lists

List content is now exported. Indentation may differ slightly and exact numbered markers may not always be preserved, but the content itself makes the journey – ready to work with inside GraFx Studio.

Nested text frames and frames in shapes

Nested text frames and frames inside shapes are now detected and handled during export. The preflight report surfaces these elements clearly, giving you the choice to convert to PDF or ignore – so nothing is silently dropped.

Locked layers exported as PDF

Previously, locked layers were skipped entirely during export. Now they are exported as PDF assets, preserving their visual appearance in the converted layout.

Smarter preflight messages

Preflight warnings are now more specific and easier to act on – so you spend less time guessing what needs attention before export.

---

Adobe Photoshop Plugin – What's New

The Photoshop plugin gets the same text column and list support in this release, bringing it in line with InDesign for these common layout structures.

• Text columns – text layers with column layouts are now supported during export.
• Bullet and numbered lists – list content is exported, with the same indentation and marker caveats as InDesign.
• Enhanced preflight warnings – more detail on unsupported effects, so you know exactly what to expect before the export runs. Note: some effect names in preflight messages differ from Photoshop's UI (for example, Satin appears as chromeFX).

---

Fidelity Fixes Across Both Plugins

Beyond the new features, v1.3.0 includes a targeted round of fixes that improve how existing designs convert:

InDesign: frame opacity for shapes; shapes with modified paths; position of rotated triangles; linked (threaded) text frames; crop of locked image layers; image crop in custom shapes.

Photoshop: export of shapes without a strokeStyle object; rounding of numeric properties during conversion.

Each fix addresses a specific case where a design element was not converting as expected – reducing the manual cleanup required after import.

---

The goal of the InDesign and Photoshop plugins has always been the same: let designers start in the tools they know, then bring those designs into GraFx Studio where automation, data-driven output, and scalable content creation take over. Every improvement to conversion fidelity means less time fixing imports and more time building layouts that work at scale.

v1.3.0 moves that goal meaningfully forward.

• Adobe InDesign Plugin documentation
• Adobe Photoshop Plugin documentation

Deploy Components Across Environments with the CHILI GraFx Environment API

Components in GraFx Studio already changed how design teams work – build a reusable design element once, and every layout that uses it updates automatically. But for teams managing multiple environments, there has been a missing piece: a reliable, programmatic way to distribute those components as part of a larger package.

The CHILI GraFx Environment API now fills that gap.

---

Import Components from a Plugin Export – via API

Plugins are installable bundles that can include GraFx Studio components alongside other resources. With this update, you can now import those components directly through the Environment API when processing a plugin export.

This means components are no longer something you need to configure manually in each environment. They travel with the plugin package – and the API handles the import.

• Distribute components as part of a plugin: Bundle your reusable design elements alongside other resources and ship them together as a single installable package.
• Deploy programmatically: Process plugin exports through the Environment API and have components land exactly where they need to be – no manual steps required.
• Scale across environments: Whether you're managing a sandbox, a staging setup, or multiple production environments, components can now be deployed consistently and repeatably through code.

---

Why This Matters for Teams Building at Scale

Components are most powerful when they are shared. A pricing block, a product badge, a branded footer – these are the elements that define visual consistency across campaigns and channels. When they live inside a plugin, they become part of a governed, distributable design system that can move across environments as your operations grow.

For developers and platform teams, this update removes a meaningful friction point from the deployment workflow. Previously, getting components into a new environment required manual intervention. Now, the Environment API handles it as part of the plugin import process – consistent, repeatable, and ready to plug into any automation pipeline.

This is especially valuable for:

• Agencies and studios managing design systems across multiple client environments
• Enterprise teams rolling out brand-approved components to regional or departmental environments
• Integration builders who need components to be part of a fully automated provisioning workflow

---

Components + API = Scalable Content Operations

Components in GraFx Studio give designers a foundation that compounds in value over time. Every element built as a component is one fewer element rebuilt next quarter. The Environment API now extends that value beyond the design workspace – into the infrastructure layer where environments are provisioned, maintained, and scaled.

The result is a tighter connection between design systems and headless production workflows. Components can now be part of how you build and deploy CHILI GraFx environments, not just how you design within them.

---

Explore the full Environment API reference in the Developer Center.

Components – Build Once, Reuse Everywhere with GraFx Studio v1.4

Every production team has design elements they rebuild from scratch – again and again. A pricing block here, a product ad there, a branded footer in every template. GraFx Studio v1.40 ends that cycle with Components, a foundational new capability that lets you design an element once and reuse it across as many templates as you need.

---

Components – Design Once, Update Everywhere

Components are reusable design elements you place inside templates. Build a pricing block, a product badge, or any branded element once – then drop it into as many templates as you need. When you update the component, every template using it updates automatically.

• Place from the Resources panel: Add components directly into your template without rebuilding from scratch.
• Multiple instances per page: Use the same component several times on a single page, each with its own independent data via variable mapping.
• Full design system support: Each component carries its own layouts, Brand Kit, variables, and actions.
• Flexible fill modes: Choose how a component fills its frame – Scale (matches by aspect ratio), Resize (uses anchoring and copyfitting), or Scale and resize (combines both).

The real power is in the update model. Change a component once, and every template that references it reflects that change automatically. For teams managing large template libraries across brands and campaigns, this is a significant reduction in repetitive production work.

Variable mapping is per instance – a template with three instances of the same component can give each its own independent data.

Learn more: Components concept · Build a component · Use components in a template

---

Other features in this release:

Give End Users Crop Control – On Your Terms

Template designers can now decide whether end users are allowed to crop images within a frame. It is a per-frame setting, disabled by default, so you opt in only where it makes sense.

When enabled, end users see a crop icon and can drag the image within the frame. The frame size and position stay fixed – so layout integrity is never at risk.

• Fit, Fill, or Smart Crop frames: Each image gets its own individual crop.
• Manual Crop frames: The crop area is shared across all images in the frame.

This gives production teams a precise way to open up creative flexibility for end users without compromising brand consistency or layout structure.

---

Connector Shared Header Value

For connector developers, there is now a way to set a header value that applies across all instances sharing the same remote connector ID. Pass a shared API key or session token once – without configuring it per instance. A small change that removes meaningful friction from connector setup and maintenance.

---

Font Size Constraint On by Default

When text editing constraints are enabled on a text frame, the font size constraint is now on by default. Previously it was off, which could produce unexpected results when restricting all text editing properties. This brings behavior in line with what designers actually expect.

---

Components alone make v1.40 a significant release for any team managing templates at scale. Combined with end-user crop control and a round of targeted fixes, this update moves GraFx Studio meaningfully forward – less repetition, more control, and more confidence in every output.

Know Your Templates Better: Creation and Modification Dates Now in the Environment API

When you're managing a growing library of templates across environments, keeping integrations in sync with what's actually changed – and when – can be a real challenge. Without reliable timestamp data, you're left guessing which templates are fresh, which have been updated, and which haven't been touched in months.

The CHILI GraFx Environment API now gives you that clarity.

---

Retrieve Template Timestamps Directly from the API

Two new fields are now available on template responses: DateCreated and LastModifiedContentUtc.

• DateCreated – the date and time a template was first created in the environment.
• LastModifiedContentUtc – the date and time the template's content was last changed.

Both fields are returned on the template list endpoint and the individual template endpoint:

GET /api/v1/environment/{environmentId}/templates
GET /api/v1/environment/{environmentId}/templates/{templateId}

No additional configuration required – the data is there when you need it.

---

What You Can Do With This

Timestamp data unlocks a range of practical use cases for developers and teams building on top of CHILI GraFx:

• Sort by recency: Surface the most recently created or updated templates at the top of a list, so end users always start from the freshest design.
• Detect changes since last sync: Use LastModifiedContentUtc to identify which templates have been updated since your integration last ran – making incremental sync workflows far more efficient.
• Display audit information: Show creation and modification dates inside connected systems, portals, or dashboards where teams need visibility into template history.
• Drive automation logic: Trigger downstream processes – approvals, notifications, or output jobs – based on when a template was last modified.

---

Built for Integration-Heavy Workflows

For teams running CHILI GraFx as part of a larger MarTech stack, this update removes a common friction point. Previously, tracking template history required workarounds or manual checks. Now, the information is available directly through the API – consistent, reliable, and ready to plug into whatever system you're building.

Whether you're maintaining a self-serve content portal, running automated batch output, or keeping an external asset management system in sync with your CHILI GraFx environment, DateCreated and LastModifiedContentUtc give your integration the context it needs to stay accurate.

---

Explore the full Environment API reference in the Developer Center.

Sharper, More Detailed Product Images – GraFx Genie Product Image Creator Just Got Better

The quality of your product visuals directly affects how your brand is perceived. Blurry edges, flat composition, or images that simply don't look polished enough – these are the kinds of details that erode trust before a customer even reads a word of copy.

The GraFx Genie Product Image Creator in GraFx Labs just raised the bar.

---

A Smarter AI Model, Better Results – Automatically

The AI model powering the Product Image Creator has been upgraded. The result: noticeably improved image quality across the board.

Product images now render with:

• More accurate detail – finer textures, cleaner edges, and truer-to-life product representation
• Better composition – outputs that feel considered and visually balanced
• Sharper results – higher clarity that holds up at scale and across formats

And the best part? You don't need to change a thing. No new settings to configure, no workflow adjustments required. The improvement is built into the model itself.

---

What the Product Image Creator Does

For teams who haven't explored it yet, the GraFx Genie Product Image Creator is an AI-powered tool inside GraFx Labs that lets you generate and iterate on product visuals directly within CHILI GraFx.

You can:

• Generate new images from a text prompt
• Start from an existing brand-approved asset in GraFx Media and augment it
• Upscale generated images for higher-resolution output
• Save results locally or directly back to GraFx Media for reuse

Whether you need a fresh visual for a campaign or want to explore new directions without a full photoshoot, the tool gets you from brief to image in minutes.

---

Built for Experimentation, Grounded in Brand Control

The Product Image Creator lives in GraFx Labs – a dedicated space inside CHILI GraFx where experimental capabilities are available for teams to explore and validate before they become part of the core platform.

Good to know: GraFx Labs features are experimental. They can change or be removed at any time. The goal is to validate ideas and capture real-world feedback.

Generated images are charged as digital PNG renders, keeping billing transparent within your existing CHILI GraFx usage model.

---

If you've been using the Product Image Creator since its launch, this upgrade delivers meaningfully better output with no extra effort on your end. If you haven't tried it yet, now is a good time to start.

Explore GraFx Genie Product Image Creator

Manage Tags Programmatically: Tags API Endpoints Now in the Public Environment API

Template libraries grow fast. And when they do, the challenge shifts from creating templates to finding the right one at the right moment. Tags in GraFx Studio already solve that for designers working in the UI – now, the same organizational power is available to developers and integrators through the public Environment API.

---

Tags, Now Fully Accessible via API

Tags let you label and organize templates. You can group templates by brand, campaign, product line, or any other dimension that reflects how your team works.

Until now, managing tags was a manual process inside GraFx Studio.

That changes with this update. The Tags API endpoints are now part of the public Environment API, giving you full programmatic control over your tag vocabulary:

• Create tags to build and extend your organizational structure automatically.
• Update tags to keep naming consistent as your library evolves.
• Delete tags to remove labels that are no longer relevant.
• Assign tags to templates to keep your library organized at scale – without manual intervention.

All of this is available as part of your existing integration or automation workflow.

---

Why This Matters for Integrators and Automation Teams

For teams running high-volume content operations, manual tag management simply doesn't scale. When you're onboarding new brands, launching campaigns across regions, or ingesting templates from external systems, you need your organizational structure to keep pace automatically.

With Tags endpoints in the public API, you can:

• Automate library organization as part of template ingestion pipelines – tags are applied the moment a template is created.
• Sync tag structures across environments or with external systems, keeping everything consistent without manual overhead.
• Build smarter integrations that surface the right templates to the right users based on dynamic tag filtering.

This is especially valuable for agencies managing templates across multiple brands, and for enterprise teams where template libraries span dozens of campaigns and channels.

---

Built on a Foundation Designers Already Use

The Tags API reflects the same logic that designers rely on in GraFx Studio. Tags are a management resource – they don't affect template behavior or output. They exist purely to help teams find and organize what they need, faster.

Now that foundation is fully accessible in code. Whether you're building a custom integration, automating content operations, or managing a library at scale, Tags give you a clean, flexible layer of organization that grows with your workflow.

---

Learn More

• Tags concept
• Environment API reference

Smarter Connector Management and a Cleaner Platform Experience in CHILI GraFx

Managing connectors across a growing environment shouldn't mean opening each one individually to check for updates, or navigating deep into settings just to set a default. This platform update removes those small but persistent friction points – and adds a few quality-of-life improvements that make working in CHILI GraFx feel more intuitive every day.

---

Know When a Connector Update Is Ready – Without Hunting for It

Connectors are how CHILI GraFx links your design workflows to the external systems your team already relies on – DAMs, PIMs, data sources, and more. Keeping them up to date matters. But until now, checking for available updates meant opening each connector individually.

That changes with update notifications. When a new version of an installed connector is available, a notification badge appears directly on the connector – both in the connector list and inside connector settings. You can see at a glance which connectors have an update ready, without any manual checking.

• Instant visibility: Update badges surface right where you manage connectors.
• No more manual checks: Spot available updates across all your connectors in one view.
• Stay current with less effort: Keeping integrations up to date is now a matter of noticing, not searching.

---

Set a Default Connector in Fewer Clicks

Designating a default connector is a common task – and it used to require navigating into connector settings to do it. The Set as default option has moved to the three-dot menu directly on the connector list, putting the action exactly where you're already working.

The option is disabled automatically if the connector is already set as default, so there's no ambiguity about the current state.

• Faster workflow: Set a default without leaving the connector list.
• Less navigation: One less trip into settings for a routine action.
• Clear status: The disabled state makes it obvious when no action is needed.

---

Dates Now Reflect Your Local Timezone

Date and time values in environment-level tables – including Tags and Output tasks – now display in your local timezone rather than UTC. If you ever need the original server time, hover over any date to see it in a tooltip.

This is a small change with a real impact: timestamps that actually match your working context make it easier to track activity, coordinate with your team, and understand when things happened.

---

New Resources Appear at the Top

Tags, output settings, output tasks, user interfaces, integrations, and subject types now sort by creation date descending by default. The most recently added items appear at the top of the list.

When you've just created something new, you shouldn't have to scroll to find it. This default sort order makes that a non-issue.

---

Connector Authentication Fix

A bug in connector Browser authentication has been resolved. Previously, setting Browser authentication to [None] while a Server authentication type was already configured incorrectly triggered a validation error. Browser and Server authentication can now be managed independently, without either configuration interfering with the other.

---

These updates reflect a consistent focus on reducing the small friction points that slow teams down. Better connector visibility, faster defaults, accurate timestamps, and smarter sorting – each one a step toward a platform that works the way your team actually works.

Learn more:

• Connector Version Updates
• Set a Default Connector

More Control, Less Repetition: GraFx Studio v1.39

Every template designer knows the tension between giving end users creative freedom and keeping output on-brand. Too much freedom and layouts break. Too little and every small copy change becomes a support request. GraFx Studio v1.39 resolves that tension with a precise new set of text constraints – and adds a handful of improvements that make building and integrating templates faster and more reliable.

---

Text Constraints – Define Exactly What End Users Can Touch

Template designers can now set fine-grained constraints on text frames, controlling what end users are allowed to do when they open a template in Studio UI.

There are two layers of control:

Frame-level constraints – decide whether the text frame itself can be moved, resized, or rotated. Lock down the layout structure while still allowing the text content to be edited.

Inline editing constraints – let end users edit text directly inside the frame, with you choosing exactly which formatting options are available:

• Paragraph styles – expose only the styles you've approved from your Brand Kit.
• Character styles – same principle: you choose which are available.
• Brand Kit colors – limit color choices to on-brand options only.
• Font size – enable size editing with a configurable minimum and maximum range, so nothing goes too small or too large.

All constraints are disabled by default. You opt in only where it makes sense, frame by frame.

Inline editing is only available on text frames that do not use variables. Frames with variables continue to use the standard variable editing experience.

The result: end users get a focused, guided editing experience. Designers keep full control over brand consistency and layout integrity.

Learn more about User Constraints for Text Frames

---

Duplicate Pages – Build Multi-Page Documents Faster

Building a multi-page document with similar layouts used to mean rebuilding each page from scratch. Not anymore.

GraFx Studio now includes a Duplicate option in the page context menu. Duplicate any page and use it as the starting point for a new variation – keeping your layout, frames, and structure intact while you adjust the content.

For teams producing brochures, catalogs, or any document where pages share a common structure, this is a meaningful reduction in repetitive work.

---

Anchored Frame Duplication Now Works as Expected

Duplicating a frame that uses anchoring now produces a correctly anchored copy. Previously, duplicated anchored frames could lose their anchoring configuration – making it unreliable to build layouts by duplication.

This fix makes anchored frame duplication a dependable part of your layout workflow.

---

Unique IDs in Template JSON – Better Foundations for Integrations

For developers building automations or integrations on top of GraFx Studio, this is a quiet but significant improvement.

Layout, page, and frame objects in the GraFx Studio template JSON now each carry a unique ID. That gives integrators a stable, predictable reference for every element in a template – useful any time you need to address a specific frame, page, or layout by ID in an automation workflow.

---

Text constraints alone make v1.39 a meaningful release for any team running self-serve content workflows. Combined with faster page duplication, reliable anchored frame copying, and a stable round of fixes, this update gives designers more tools to build templates that are both flexible for end users and consistent in output.

GraFx Experience 2.111: Govern Who Sees What Across Your Entire Portal

When a self-serve content portal grows to serve dozens of teams, regions, or brands, the question of access becomes critical. Who should see which templates? Which projects belong to which users? Without clear answers, portals become cluttered, workflows break down, and brand governance slips.

GraFx Experience 2.111 addresses this directly with global permission groups – giving administrators precise, application-wide control over what every user can access.

---

Global Permission Groups for Templates

Administrators can now define permission groups and assign them to users, controlling exactly who has access to templates, projects, and production outputs across the entire GraFx Experience application.

This is governance at scale. Rather than managing access on a case-by-case basis, admins build groups that reflect how their organization actually works – by team, region, brand, or role – and assign users accordingly. A user's effective permissions are the sum of the groups they belong to, so access can be layered and combined as needed.

What this means in practice:

• Scoped template access: Users only see the Design Systems and layouts relevant to their role. A regional marketing team sees their market's templates; a global brand team sees everything they need.
• Pre-configured field filters: Admins can configure field filters in the content store and project elements in advance, so users arrive in a focused, relevant workspace rather than an unfiltered library.
• Personal work stays personal: Users always retain full access to the projects and production outputs they have created themselves – regardless of group configuration.

The result is a portal that feels purpose-built for each user, even when hundreds of people share the same environment.

---

Why This Matters for Distributed Teams

GraFx Experience is designed for organizations where content creation is distributed – franchises, field marketing teams, retail networks, or global brand operations. In those environments, showing every user every template is not just unhelpful, it creates friction and increases the risk of off-brand output.

Global permission groups close that gap. Admins shape what each user sees and does without changing the underlying content. The design system stays intact; only the view changes.

---

Also improved in this release:

• Dark theme support on access denied pages: The 403 access denied page now respects the dark theme when enabled, keeping the interface consistent for users who prefer it.
• Space chooser dropdown fix: The space chooser dropdown no longer appears behind the side menu in the editor, resolving a visual overlap that affected navigation.

---

Permission groups bring the same governance logic that powers GraFx Studio design systems into the GraFx Experience portal layer – so the right content reaches the right people, every time.

More Control Over AI-Powered Image Intelligence: Subject Types Now Accessible via API

Smart Crop and GraFx Genie's Vision AI don't work by magic – they work by understanding what to look for. Subject types are the user-defined categories, like "person" or "product," that tell the Vision AI where to focus in an image. Until now, managing those categories was a manual task. That changes with this Environment API update.

---

Retrieve and Update Subject Types Programmatically

You can now read and write subject type data directly through the API – for both media assets stored in GraFx Media and assets pulled in from external sources.

Retrieve all subject types at once:

GET /vision?expand=allSubjectTypes

Or query a specific subject type for a single asset:

GET /media/{mediaId}/vision/subject-types/{subjectTypeId}
GET /external-media/{externalMediaId}/vision/subject-types/{subjectTypeId}

Update subject types – individually or in bulk – using the extended endpoints:

PATCH /media/{mediaId}
PUT /external-media/{externalMediaId}/vision

No manual UI work required. The full read-write cycle for subject type data is now available in code.

---

Why Subject Types Matter

Subject types are the foundation of how GraFx Genie's Vision AI interprets your image library. When a subject type is correctly defined, Smart Crop knows exactly where to focus – keeping your subject centered, your layout intact, and your output consistent across formats and channels.

For teams managing large asset libraries or ingesting images from external DAM systems, maintaining accurate subject type data at scale has historically required manual intervention. With these new API endpoints, that process can be automated from end to end.

• Automate subject type assignment as part of your asset ingestion pipeline – the moment a new image enters your environment, the right categories can be applied.
• Sync Vision AI metadata across environments or with external systems, keeping Smart Crop behavior consistent wherever your assets are used.
• Manage external media assets with the same precision as native GraFx Media assets – the external-media endpoints bring parity to both workflows.
• Bulk update subject types when your categorization structure evolves, without touching each asset individually.

---

A Cleaner Font List in Your Integrations

This release also includes a small but meaningful improvement for integrations that surface font lists to end users. When a font preview can't be rendered, the list now displays fallback text instead of leaving a blank space.

It's a cleaner experience for anyone selecting fonts inside a connected portal or custom interface – no more unexplained gaps in the list. A full fix for fonts that still don't preview correctly is planned for a future release.

---

For teams building on top of CHILI GraFx, these additions extend the API's reach into one of the platform's most powerful AI-driven capabilities. Subject type control is no longer a manual step – it's part of your automation workflow.

Explore the CHILI GraFx API documentation

No More Guesswork: Existing CHILI GraFx Users Now Get a Clear Invitation When Added to a New Subscription

Getting access to a new subscription should be straightforward. But for users who already have a CHILI GraFx account, the experience of being added to a second subscription could leave them wondering: did something change? Do I need a new login? Where do I even start?

A small but meaningful update to the CHILI GraFx Platform API removes that uncertainty entirely.

---

Existing Users Now Receive an Invitation Email

When an existing CHILI GraFx user is invited to a new subscription, they now receive an email notification that tells them exactly what they need to know:

• The name of the subscription they've been invited to – so there's no confusion about which account or organization this relates to.
• Clear guidance to sign in with their existing credentials – no new account to create, no password reset required.

It's a direct, informative message that gets users into the right place without friction.

---

Why This Matters

In organizations running multiple subscriptions – agencies managing several client accounts, enterprises with distinct business units, or teams expanding their CHILI GraFx footprint – users often need access across more than one subscription.

Before this update, an existing user added to a new subscription received no notification at all. They had no way of knowing access had been granted unless someone told them directly. That created unnecessary back-and-forth, support requests, and delays in getting people productive.

Now, the platform handles that communication automatically. The moment an admin adds an existing user to a subscription, the user is informed – with the right context and the right next step.

---

A Better Experience for Admins and Users Alike

For Subscription Admins and Environment Admins managing access across teams, this update means one less thing to coordinate manually. You grant access through the platform; the platform takes care of letting the user know.

For users, it means clarity from the start – a named subscription, a familiar login, and no ambiguity about what to do next.

---

This is the kind of improvement that doesn't change what the platform can do, but meaningfully improves how it feels to use it. Clear communication at the moment of access is a small detail that makes a real difference at scale.

Read more in the Developer Center.

GraFx Studio Photoshop Plugin 1.2.1: Smoother Imports for Complex Documents

Photoshop documents are rarely simple. Layers stack up, effects accumulate, and over time a working file can contain all kinds of structural quirks – including groups that carry effects but hold no layers inside them. Until now, that kind of document could stop a GraFx Studio import in its tracks.

Plugin 1.2.1 fixes that.

---

Empty Effect Groups No Longer Block Your Import

Some Photoshop documents include groups that have effects applied – such as Drop Shadow or Bevel & Emboss – but contain no layers inside them. These empty effect groups caused the import process to fail entirely, leaving teams unable to bring their work into GraFx Studio without first hunting down and removing the offending groups.

With this update, those empty groups are simply skipped during import. The rest of the document loads correctly, and your workflow continues without interruption.

• No manual cleanup required: Affected documents now import without needing to be restructured first.
• Reliable imports for complex files: Documents built up over time – with all their accumulated quirks – are handled more gracefully.
• Less time troubleshooting, more time producing: The path from Photoshop to GraFx Studio stays clear.

---

Why This Matters

The GraFx Studio Photoshop plugin exists to bridge the gap between creative work done in Photoshop and the automation power of GraFx Studio. The goal is straightforward: bring your designs in, then let GraFx Studio handle the scaling, personalization, and multichannel output.

Anything that interrupts that import – even an edge case like an empty effect group – breaks the flow and adds friction for designers and production teams. This fix removes one more obstacle from that path.

If you've previously run into failed imports on documents with complex layer structures, this update is worth applying.

---

Read more about the Adobe® Photoshop® plugin