iMazing Release Notes

Version: 2.3.0 (406703)

Release date: Wed, 23 Sep 2026 11:18:33 +0200

What's New in iMazing Profile Editor 2.3.0 for macOS

Improvements in 2.3.0

Adopted modern macOS UI style
Added Finder Quick Actions for unsigning profiles and for resetting profile identifiers
A shortcut to the Quick Actions approval location in System Settings is now available in the integrations tab of the app settings
App drag and drop support is now expanded from PPPC tables to any table that takes bundle ID, code requirement, and/or team ID
Managed Client: Forced is now the default payload container for non-official and third-party domains for maximum MDM compatibility
Managed Client payloads now participate in conflict resolution for domains that do not support multiple payloads: these can have one General or Managed Client: Forced payload, and one Managed Client: Set-Once payload
Copying, pasting, dragging, and importing payloads now preserve the payload container type of the source payload
In sections where properties are split into groups, group selectors can now feature an overflow menu instead of having to truncate titles
Descriptions of boolean properties are hidden by default; they now unhide to highlight matching search terms
Supervision requirement is now indicated by the platform tags instead of separate text labels

Other notes for 2.3.0

This version of iMazing Profile Editor requires macOS Sonoma (14.0) or higher

What's New in iMazing Profile Editor 2.2.1 for macOS

Fixes in 2.2.1

Fixed an issue that prevented saving profiles when a payload was imported from JSON with null values
Fixed the dragging border discoloration on MacBook Neo when the theme color is set to 'This Mac'

What's New in iMazing Profile Editor 2.2.0 for macOS

Improvements in 2.2.0

Payload copy-paste is now available between profile windows as well as to and from text editors
When pasting-in from a text editor, an attempt is made to auto-detect the payload type
Payload drag and drop is now available between profile windows as well as to and from Finder windows
When dragging-in from Finder the Payload type is taken from the file content when available and from the file name otherwise
Payload drag and drop as well as copy-paste features support both plist and JSON. Drag-out to Finder is plist only
Payload import and export operations now too support JSON alongside previous support for plist
The profile signing field now labels expired identities and displays serial numbers when common names are not unique
Alerting users about unavailable signing identities now takes place on profile-save instead of on profile-load
System Settings is now opened on the profiles section when selecting to install an open profile
Finder should now prefer launching a stand-alone installation of the app over a bundled one when both are available
On macOS Tahoe (26.0), the app icon now adapts to the user-set icon style

Fixes in 2.2.0

Fixed an ambiguity issue that could cause an incorrect signing identity to be used when a selected identity shared its common name with other installed identities
Resolved the incorrect marking of profiles as unsaved when concluding profile installation

What's New in iMazing Profile Editor 2.1.2 for macOS

Fixes in 2.1.2

Fixed an issue that led to an app crash during Total App Setup analysis of certain app bundles
Fixed an issue that led to an app crash when importing payloads on macOS versions prior to Sequoia (15.0)
Fixed an issue with generating a timestamp when converting Forced MCX payloads to Set-Once
Fixed the incorrect entry field for code requirement in the Parental Controls: Application Restrictions section

What's New in iMazing Profile Editor 2.1.1 for macOS

Fixes in 2.1.1

Fixed incorrect grouping and exclusion of a Restrictions preference key
Fixed undesired activation of a shortcut key in Total App Setup
Relaxed a limitation on the types of certificate payloads available for selection from drop-down fields

What's New in iMazing Profile Editor 2.1.0 for macOS

Improvements in 2.1.0

Total App Setup now better detects app PPPC needs and includes support for additional services
Total App Setup now supports iOS apps, for which it can automatically configure Notifications payloads
The App Inspector now supports iOS apps
Apps can now be dragged and dropped into PPPC service tables for automatic bundle ID and code requirement entry
The payload type of a payload imported from plist can now be manually entered
The profile identifier prefix, which distinguishes locally created profiles from MDM ones, now defaults to the name of the editing app instead of the authoring machine, and can now also be set to none

Fixes in 2.1.0

Fixed a regression in highlighting search matches on new payloads
Fixed an issue that rendered ineffective the choice on the save-panel to stop signing a profile
Fixed a section selection glitch that appeared when removing unfamiliar sections

What's New in iMazing Profile Editor 2.0.0 for macOS

Improvements in 2.0.0

Introducing Total App Setup. iMazing Profile Editor can now scan macOS apps for configuration needs and automatically set them up
Payloads can now be imported from plist
Payloads can now be imported from other profiles
Payloads can now be exported to shell script (macOS user preference payloads only)
Payload export to plist is now also supported on unfamiliar payloads
Common payload properties can now be included when exporting payloads to plist
Properties referencing other payloads (e.g. certificate UUID in a Wi-Fi payload) now offer easy selection from a list
All profile identifiers and UUIDs can now be reset from the menu and are reset by default on a profile Save-As
Managed Client (MCX) payloads can now be displayed and edited
Payloads can now be converted to and from MCX (macOS user preference payloads only)
visionOS configuration and validation are now supported
Stand-alone versions of the app will no longer terminate when the last window is closed
An example manifest bundle is now included inside the app bundle
The UI has received a refresh

Fixes in 2.0.0

Fixed an issue with evaluation of presence conditionals
Fixed a regression in the appearance of supervision-required labels
Fixed the unresponsiveness of the search shortcut when editing in a text field
Prevented unintentional shuffling of array items when a table header is clicked
Resolved the unnecessary validation of excluded properties
Property presence documentation updated to distinguish conditional requirement
Resolved an issue that caused required properties to be set to their default value on profile load
Fixed visual glitches specific to macOS Monterey (12.0)
Fixed an issue that locked the UI after saving invalid profiles to the library in the version bundled with iMazing

Other notes for 2.0.0

This version of iMazing Profile Editor requires macOS Monterey (12.0) or higher

What's New in iMazing Profile Editor 1.9.2 for macOS

Fixes in 1.9.2

Fixed regression in X.500 fields

What's New in iMazing Profile Editor 1.9.1 for macOS

Improvements in 1.9.1

In accordance with advice from Apple, iMazing Profile Editor will no longer rotate profile or payload UUIDs when saving profile changes
Table-nested boolean properties now better support the latest improvements to the PPPC section

Fixes in 1.9.1

Fixed a number of visual issues

What's New in iMazing Profile Editor 1.9.0 for macOS

Improvements in 1.9.0

The new App Inspector tool makes it easy to discover and copy app properties such as bundle ID, team ID, and code requirement which are required for various configuration payloads
Dictionary properties can now partake in exclusion of other properties, improving interactivity in the Wi-Fi section

What's New in iMazing Profile Editor 1.8.0 for macOS

Improvements in 1.8.0

A new information popover now features expanded documentation, availability, and community notes for both configuration payloads and properties
String fields can now suggest common values while still allowing custom ones. For example the Extension Identifier field in the Single Sign-On Extensions section

Fixes in 1.8.0

Fixed regression in the evaluation of 'contains-any' conditionals that target array properties

What's New in iMazing Profile Editor 1.7.4 for macOS

Improvements in 1.7.4

Microsoft Edge's ManagedFavorites as well as both Google Chrome's and Brave's ManagedBookmarks are now fully supported thanks to new non-homogeneous array handling capabilities
Plist files loaded into table-nested arrays are now checked for conformance with their property domain manifest

Fixes in 1.7.4

Fixed different issues with comma-separated array entry fields

What's New in iMazing Profile Editor 1.7.3 for macOS

Fixes in 1.7.3

Fixed incomplete manifest processing

What's New in iMazing Profile Editor 1.7.2 for macOS

Improvements in 1.7.2

Added watchOS as a configurable platform

Fixes in 1.7.2

Fixed incorrect preference key maximum version evaluation
Fixed missing filtering and term highlighting on additional section payloads
Resolved incorrect display of certain table-cell custom dictionaries
Resolved incorrect assignment of empty values to table-cell arrays when required
Resolved incorrect validation of required arrays
Addressed inability to load certain certificate formats as root

What's New in iMazing Profile Editor 1.7.1 for macOS

Fixes in 1.7.1

Resolved manifest optimizations not updating on unchanged remote manifests

What's New in iMazing Profile Editor 1.7.0 for macOS

Improvements in 1.7.0

Unfamiliar payload keys (those loaded from file but not matched to keys in the payload manifest) are now kept on save and can be optionally removed
All Plist data types are now supported in table fields, adding Data, Date, custom Array, and custom Dictionary
All table input fields now support interaction and type adapters similar to their free-standing counterparts

Fixes in 1.7.0

Fixed issues that prevented correct loading, entry, and saving of data in some tiered array properties, which affected sections such as Parental Controls: Application Access, Nudge, and NoMAD Shares
Fixed an issue that prevented text fields from expanding along with their table columns
Fixed an issue that delayed validation for table fields values

What's New in iMazing Profile Editor 1.6.4 for macOS

Improvements in 1.6.4

Key description can now be optionally shown for boolean properties (checkboxes)
Table rows can now be duplicated when working with array-based properties

Fixes in 1.6.4

Fixed an overflow in the width of the main preferences page in certain sections
Fixed an issue that prevented an eventual profile window close when during the action the profile is saved to the profile library
Fixed an issue that caused the Restrictions and Notifications sections to lose support for an operating system in rare occasions

What's New in iMazing Profile Editor 1.6.3 for macOS

Improvements in 1.6.3

The Profile Signing field now indicates which identities are trusted on the signing computer
The Root Certificate manifest now has its own section

Fixes in 1.6.3

Fixed cell editing in multi-column tables
Fixed label truncation in property group selectors during search
Profiles with self-closing data tags are now supported

What's New in iMazing Profile Editor 1.6.2 for macOS

Improvements in 1.6.2

iMazing Profile Editor now bundles the latest preference updates introduced with iOS 16.

Fixes in 1.6.2

Resolved a condition that led to reversion of entered field value when pressing the Escape key.
Resolved a condition that prevented dismissal of certain notices on macOS Monterey.
Fixed an issue that prevented a setting in the save panel to take effect.
Fixed an issue that in some cases prevented immediate evaluation of preference key requirement.
Fixed a rare visual glitch in the display of platform tags.
Fixed a visual glitch in sizing data field buttons.

What's New in iMazing Profile Editor 1.6.1 for macOS

Fixes in 1.6.1

Fixed an issue that led to app crashes on a small set of payloads.
Fixed a regression that prevented interacting with custom dictionary properties.

What's New in iMazing Profile Editor 1.6.0 for macOS

Improvements in 1.6.0

Platform tags now feature version and lifecycle stage information.
Platform tags added to configured sections and to individual preference keys. On keys, tags appear by default only if the individual key's versions are divergent from the payload's.
Target devices version range can now be entered to receive out-of-range alerts on configured preference keys.
Key requirement is now ignored in nested-required keys whose container is not required and is not written out to the profile.
Documentation buttons added to individual preference keys where available.

Fixes in 1.6.0

Fixed an issue that affected payload scrolling with a mouse.
Fixed an issue that prevented saving profiles with VPN tunnels configured.