
When a Photopea script creates files through a filesystem-style operation such as Document.exportDocument(), Photopea offers a ZIP archive after the script finishes. That delivery is different from assuming a desktop script directly wrote each output into a chosen local folder. Inspect and extract the actual archive before calling the export complete.
Identify which output mechanism the script uses
Photopea's scripting documentation describes the ZIP behavior for created files. It separately documents Document.saveToOE() for sending binary data to an outer environment. These are different delivery contracts.
For a hypothetical script producing several product proofs, decide whether the person expects a downloadable archive or an embedding application expects a returned binary. Do not look for an archive if the integration deliberately uses another documented transport, and do not treat an outer-environment callback as an ordinary local download.
The source establishes output behavior; it does not establish that an arbitrary Photoshop script's filesystem paths are available in a browser.
Wait for the script's output stage
The documented archive is offered after script completion. A visible change on the canvas can occur before the entire script has completed or produced its intended files. Distinguish editing progress from file delivery.
Use a reviewed, small script and harmless working document when checking an unfamiliar export workflow. The File > Script window provides the editing and Run controls, but do not paste unreviewed automation merely because this guide describes the output format.
If no archive is offered, inspect whether the reviewed script actually created export files, whether it completed and whether it used the expected output mechanism. Do not repeatedly launch the full batch solely because the browser's download folder looks unchanged.
Inspect the extracted set
Open the downloaded ZIP and extract it to an identifiable folder. For the proposed proof set, compare filenames and visible contents with the intended document list. Check that a recognizable item appears in the correct output rather than relying on the archive's presence alone.
A ZIP can be delivered successfully while containing the wrong pictures. Conversely, an edited canvas does not establish that any files were packaged. Keep those acceptance questions separate.
The portable filenames and paths guide helps identify files after extraction. If a reusable automation resource is also being supplied, the workflow recovery guide explains the adjacent distinction between an asset and instructions needed to recreate it; its ComfyUI mechanisms are not Photopea scripting APIs.
Preserve the intended destination
Move the verified outputs into the agreed delivery location only after extraction and review. An offered download is not evidence that a shared drive, website or customer folder was updated automatically. State which artifact was created and where the recipient can actually retrieve it.
Related tasks
- Why Does My Photoshop Batch Action Save Files Under the Same Name?
- Apply Data Set or Export Data Sets as Files? Preserve Your Photoshop Template
- Why Does My Artwork Package Work Here but Fail on the Recipient’s File Path?
Sources and scope
- Photopea - Scripts: When a script creates filesystem files, Photopea offers a ZIP containing them when execution finishes.
Based on official Photopea documentation read on October 23, 2026 (Asia/Shanghai). Any exercises are proposed checks, not hands-on tests. No script is executed by this guide; verify reviewed automation in a disposable project.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Mariya Eskina / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.