Independent public-interest evaluations of how systems respect dignity and support agency.
HXR Evaluation
Photoshop Makes You Wait to Start Save As While Another Save Finishes
Users report that older Photoshop versions let them prepare another Save As during background saving, while newer versions make them wait for the first save to finish. An Adobe-hosted Photoshop feature request from November 2025 reports that older Photoshop versions allowed a user to start Save As, edit the filename, and choose another format while a prior PSD save continued in the background, while newer versions require waiting for the first save to finish. The current HXR contributor independently reports materially similar Photoshop behavior over many years. Adobe's Photoshop documentation describes Save in Background as allowing continued work while files save. The evidence supports a durable Photoshop-specific workflow question but does not establish the current behavior on every version, a population prevalence rate, or shared mechanism with Illustrator.
- Evaluation ID
- HXR-EVAL-0028
- Status
- Open — gathering evidence
- HXR Incident connections
- 1
- Last updated
- August 25, 2026
Who and what this Evaluation covers
Naming an organization, product, service, or workflow identifies the subject of this Evaluation. It does not by itself prove which internal team caused or controls the issue.
- Organization in scope
- Adobe
- Product, service, or workflow
- Adobe Photoshop
Evaluation scope
Includes Adobe Photoshop desktop Save As behavior on the same working document while a prior Save is still active: ability to start Save As, rename, choose another format/location, defer execution safely, and avoid manual polling. Excludes Illustrator implementation, other Photoshop save-format controversies, generic background tasks, and any assumption that Photoshop and Illustrator share one implementation mechanism.
Question being evaluated
When a Photoshop document is already saving in the background, does Photoshop let the user begin and preserve a subsequent Save As operation while the first Save finishes, or does it force the user to wait and retry?
Current findings
What works well or deserves recognition
The same Adobe-hosted report states that older Photoshop versions allowed Save As preparation during background saving, which suggests the requested human workflow has existed in Photoshop before. Adobe also documents background saving as a productivity feature. These points support feasibility context but require version-specific verification.
Difficulties and opportunities to improve
The reported newer Photoshop workflow requires waiting for the current Save to finish before beginning a follow-on Save As, reducing continuity for large-file and multi-version workflows. The user must manage timing rather than expressing the next save intent once and letting the application serialize execution.
Mixed findings and limits
The evidence does not establish whether current Photoshop behavior is identical across macOS and Windows or whether format, document state, storage target, or save architecture changes the constraint. HXR does not require simultaneous writes; safe deferred execution satisfies the human objective.
How HXR would test performance
During a measurable Photoshop background Save, invoke Save As once. The user can specify destination/filename/format without waiting for the current write to finish, and Photoshop safely performs the queued/deferred operation after the original Save completes. The first Save is not canceled, corrupted, or silently superseded, and the user does not need to poll and retry.
Evidence coverage and limits
Contributor testimony plus Adobe-hosted Photoshop feature request reviewed August 24, 2026; product behavior needs current-version verification.
Connected HXR Incident reports
- Context Only: HXR-2026-0824-0001 — Illustrator Save As Was Selectable During an Active Save but Then Rejected
1 public HXR Incident report is connected to this Evaluation. Canonical roles: 0 supports; 0 partially supports; 0 narrows; 1 context only; 0 challenges. Connections are not votes and do not establish prevalence.
Technical record details
- Evaluation type
- Interface
- Benchmark posture
- Needs More Evidence
- Blue Score readiness
- Developmental Data Only
- Public revision
- 1