About Adobe Creative Cloud Packager


Creative Cloud Packager is no longer in development and no updates will be provided. Also, Creative Cloud Packager cannot be used to create packages that include Creative Cloud 2019 apps or later. Learn More.

We recommend that you use the create package workflows provided in the Adobe Admin Console.

See how to create Named User Licensing packages and Shared Device Licensing packages.

Adobe® Creative Cloud™ Packager makes it easy for you to create packages that contain Adobe Creative Cloud products and updates. These packages can then be deployed to the client machines in your organization.

Creative Cloud Packager provides workflows for both Creative Cloud for teams and Creative Cloud for enterprise.

Using Creative Cloud Packager, you create Windows or macOS packages (MSI or PKG files) and then using any third-party deployment tool that supports the deployment of native installers (for example Microsoft SCCM, Apple ARD, or JAMF Casper Suite) deploy them to client machines.

Download Creative Cloud Packager

Download Creative Cloud Packager as follows:

  • If you are a Creative Cloud for teams customer, download Adobe Creative Cloud Packager from the Admin Console.
  • If you are a Creative Cloud for Enterprise customer, download Adobe Creative Cloud Packager from the Adobe Licensing Website (LWS) or Admin Console. You also get your enterprise license key from the LWS.


It is recommended that Creative Cloud Packager should not be installed on a system where one or more Creative Suite products or Creative Cloud Manager products are installed.

Adobe Application Manager 3.1 and Creative Cloud Packager can be installed and used on the same machine. However, they should not be running simultaneously for package creation.

Advantages of deployment packages

Adobe Creative Cloud Packager provides several advantages when deploying the Creative Cloud applications across large organizations.

Silent and custom install

Deployment packages enable silent installs. A silent install requires no input from end users on the systems on which it is executed, meaning that all choices affecting what is installed and how it is installed are made before the install is performed. These choices are stored in the package.

When creating a deployment package, you choose the applications and components you want to install from the product you are packaging. When packaging products for delivery on Windows, you can choose 32-bit or 64-bit versions of the applications. You can also easily choose install options that may not be available when users install applications directly. For example, you can direct the install program to ignore conflicting processes during installation.

Easy package creation

Package creation is easy with the Creative Cloud Packager—the Creative Cloud Packager has an easy-to-use GUI that makes it simple to create a deployment package.

The packages created by the Creative Cloud Packager are in industry-standard formats (MSI in Windows, PKG in macOS) that are compatible with SCCM and ARD.

Modest system requirements

The system requirements for the Creative Cloud Packager are minimal.

Packaging versus Installation

Creative Cloud Packager does not perform an install; it creates a deployment package that records the install decisions you make ahead of time.

When you create a package using Creative Cloud Packager, you download the products and their updates. Then, you configure product options for enterprise scenarios, and generate an output in native installer formats (MSI or PKG).

The packages created are optimized for deployment using enterprise deployment tools.

Creative Cloud Packager guidelines

  • Adobe deployment packages do not support snapshot installations.
  • Adobe deployment packages cannot be used to deploy system or application configuration information other than what is explicitly described in this document. In particular, you cannot deploy application–specific preference settings.
  • You can use Creative Cloud Packager to package only the tools and services that are part of the Creative Cloud. You cannot use this tool to package to Creative Suite applications or the desktop versions of other suites.
  • In Windows, if you want to install on both 32-bit and 64-bit systems, you must create both a 32-bit package and a 64-bit package.
  • The Creative Cloud Packager does not support the Administrative install point.
  • The Creative Cloud Packager does not support NFS or SMB.
  • Do not edit the package file (MSI or PKG) created by the Application Manager. The only exception is when you want the user to specify the installation location in macOS. In this case, you must modify the Info.plist file in the generated PKG as described in the article Deploying Adobe Packages with ARD.


Do not attempt to use a PKG package to install on a Windows system.

System requirements

  Windows macOS
Operating System Windows 7 onwards (32-bit and 64-bit)
Mac OS X v10.9 onwards
Hard disk space 450 MB space available for installation 265 MB available for installation
RAM 1024 MB 1024 MB
Display Display 1,024 x 768 (minimum) or 1,280 x 800 (recommended) with 16-bit video card.
Administrator Rights

Required on the system on which you are installing Creative Cloud packager

Required on the systems where you deploy the packages

(Not required for creating the packages)

Internet Access Required on the system where you are creating the packages

Site/Port information used by Creative Cloud Packager 

For information on host/port combinations that must be allowed when logging in with an Adobe ID to download, install, and package applications using the Creative Cloud Packager; refer to section Non-browser-based services in the document, Adobe Creative Cloud Network Endpoints.

More Creative Cloud Packager tools

When you install Adobe Creative Cloud Packager, the following components are also made available. All these components are in the utilities or toolkit folder.

Adobe Update Server Setup Tool

Adobe Update Server Setup Tool (AUSST) is a platform-specific command-line tool that helps you configure your own internal Adobe Update Server. A single server can host updates for both Mac and Windows

For more information, see Using Adobe Update Server Setup Tool.

Adobe Exceptions Deployer Application

Adobe Exceptions Deployer Application provides an automated way to deploy the packages in the Exceptions folder, that is, the packages that you would otherwise deploy separately before and after deploying the main MSI or PKG file.

For more information, see Using Adobe Exceptions Deployer.

Adobe Remote Update Manager

Adobe Remote Update Manager provides a command-line interface that you can use to remotely run the Adobe Update Manager and install updates with administrative privileges.

Only users with administrative privileges can run Remote Update Manager.

For more information, see Using Adobe Remote Update Manager.

Adobe Provisioning Toolkit Enterprise Edition

Adobe Provisioning Toolkit Enterprise Edition is a command-line tool for supported platforms that helps you track and manage the licensing of Adobe® products that you have deployed in your enterprise.

Note: Use Adobe Provisioning Toolkit Enterprise Edition if you are an Enterprise, Government, or Education user and you want to serialize a trial package that you created earlier. The use flow is described in the Serializing trial packages section later in this article.

For more information, see Using Adobe Provisioning Toolkit Enterprise Edition.

Adobe IT Tools Uninstaller

The Adobe IT Tools Uninstaller provides a simple utility to uninstall the Creative Cloud Packager and other associated IT tools.

Adobe resources for IT

Adobe has a dedicated forum that covers the topic of deployment for both Creative Suite and Creative Cloud: Enterprise Deployment for Creative Cloud.

An Adobe IT-centric blog is updated regularly and covers a wide range of topics for managing Adobe software: http://blogs.adobe.com/oobe/.

For a list of the network calls made by the applications and a description of the methods for controlling service access visit this link.

Many Adobe teams have Twitter accounts and there is one dedicated to the IT tools and the topic of deployment: @Adobe_ITToolkit