The September 2025 update of Adobe Photoshop (version 26.11) is modest in scope but introduces a structural change: cross-app cloud projects. Alongside that, Adobe has added Firefly asset import and vector rendering for CJK text. The typography and Firefly updates are clear feature upgrades. The cloud projects, however, touch the way teams manage and share assets across applications.
From Libraries to Projects: what changed?
Creative Cloud has offered “Libraries” for years: shared collections of colours, brushes, symbols, and logos. Libraries are lightweight, designed to pass assets around quickly. But they do not handle project-level structure or permissions.
Photoshop 26.11 introduces cloud projects as containers for multiple file types and assets across Illustrator, Photoshop, and Adobe Express. Unlike Libraries, cloud projects can: Group full files (not just swatches or elements) into a single unit. They also can Assign user roles: editors can change content, while commenters can only review and annotate. So to Keep project-wide organisation, rather than loose collections of items.
In essence, a cloud project is Adobe’s attempt at a collaborative folder, integrated directly into Creative Cloud apps.
Collaboration: practical gains and limits
For freelancers and small studios, cloud projects could simplify version control. Instead of shuttling Illustrator vectors, Photoshop comps, and Express exports back and forth via email or cloud drives, everything lives in one Adobe-managed container.
For larger pipelines, the situation is less straightforward. Many VFX, post, and design studios already rely on dedicated asset management (ShotGrid, ftrack, or in-house DAMs). These systems support pathing, metadata, and automation in ways Creative Cloud has historically struggled with.
Questions remain open:
- How are conflicts handled if two editors open the same file?
- Does Adobe keep a file history or only the latest save?
- How are large binary files (e.g. layered PSDs >1 GB) treated inside projects?
Adobe has not provided detailed technical documentation on these points. Until clarified, projects should be considered convenience features rather than replacements for established pipeline tools.
Permissions: useful, but basic
Role-based access in cloud projects is limited to two tiers: edit and comment. Unlike enterprise DAM systems, there is no granular control over layers, linked assets, or export rights. For example, a user with “comment” rights cannot modify a PSD, but they can still see full-resolution assets. This may raise concerns in projects with strict confidentiality requirements. For teams needing more controlled distribution (for instance, advertising agencies under NDA), traditional controlled file-sharing may remain preferable.
The Firefly angle
The new Firefly integration is deliberately narrow. Firefly-generated images can be imported into Photoshop for refinement, but Firefly remains a standalone app. Edits are non-destructive, meaning the Firefly original is preserved while Photoshop creates a modified copy. This workflow may fit well with cloud projects. Teams could keep Firefly outputs and Photoshop refinements in the same shared project container, reducing file duplication across drives and emails. Still, without in-app generation, the workflow remains split across two applications.
CJK text: better previews, fewer headaches
Typography in Chinese, Japanese, and Korean (CJK) has long been one of Photoshop’s weaker areas. Raster-based previews made text appear jagged and inconsistent, especially when shared across machines. Photoshop 26.11 replaces this with vector-based rendering. On-screen previews should now match Illustrator’s fidelity, giving artists sharper results and reducing misalignment in multilingual layouts. In cloud projects, where documents may be passed between different Creative Cloud versions, this could cut down on errors.
Adoption strategy: cautious roll-out
Photoshop 26.11 is available via Creative Cloud subscriptions at no extra cost. Version rollout may vary by OS and region. For individual users, cloud projects and Firefly import may improve daily efficiency. For studios, adoption should be cautious. Cross-app projects may not play well with custom pipeline scripts or local render automation.
As always: test before deploying to production.
