# Before exporting Aquarell PSD: raster layers, text and delivery notes Language: en Canonical: [Before exporting Aquarell PSD: raster layers, text and delivery notes]() 中文：[中文 HTML]() English: [English HTML]() Published: 2026-10-22T00:00:00+08:00 Modified: 2026-10-23T10:34:07+08:00 Author: Bison Organise the layers for delivery, compare the PSD with a preview, and explain raster layers, editable text and native projects to the recipient. English translation of the [Chinese original](), translated on 2026-10-23. The article body uses automated translation; app descriptions, historical reading notes and video subtitles receive separate editorial checks. Original publication dates, attribution, code and version notes are retained. **Aquarell can export PSD files with pixel layers, but this does not mean every editing structure in the native artwork transfers unchanged to other software.** Explaining each file's purpose before handoff reduces back-and-forth more effectively than simply sending a file with a PSD extension. This tutorial is for a finished layered illustration that someone else will continue compositing, laying out, or editing at the pixel level. The goal is to organize the layers, export reference files, and check what information the recipient actually needs. ## 1. Confirm what the recipient wants to edit Divide the requirements into three types: a finished image only; separate pixel layers for compositing; or continued editing of text and internal app structures. PNG or JPEG may suffice for the first, PSD is an option for the second, and the third calls for a clearer discussion of native files and editing environments. For example, if the recipient only wants to place a leaf illustration on a poster, a transparent PNG may be more direct. Pixel layers are valuable if they want to adjust the background, subject, and shadows separately. If they want to change the heading, they cannot assume that the PSD still contains editable text. ## 2. Organize layer roles and visible content Open the Layers panel and inspect the sketch, base color, shadows, details, and text one layer at a time. Hide temporary test layers and make sure palette drafts, brush tests, and composition references have not accidentally become part of the finished image. Explain the purpose of any supporting layers that the recipient should keep. Do not merge all layers merely to make the file look tidy: merging may remove precisely the independent editing flexibility the recipient needs. Nor should you assume that native groups retain the same structure in PSD. The publicly stated scope is pixel-layer output, so plan the handoff around that. ## 3. Provide a separate, copyable version of the text If the card contains a heading, date, or explanation, save the exact text separately in the handoff notes. For example, record “Heading: Take It Slowly Today Too; Date: October 22, 2026,” and explain that the text is rendered as pixel content in the output. If the recipient needs to reset the typography, also provide the original font name and a reference font size. Whether you can transfer the font file depends on its license. Do not bundle fonts without permission, and do not treat a recorded font name as a guarantee of identical typography across applications. This simple note saves the recipient from retyping text from an image and reduces spelling and date errors. ## 4. Export the PSD, then a preview image In “Export,” choose “Export Photoshop (PSD)” and save the file through the share sheet. Export a PNG or JPEG from the same artwork state as a visual reference. Both files should represent the same revision, so the PSD is not an older version than the preview. You can distinguish the files with a shared prefix, for example `plant-card-v03.psd` and `plant-card-v03-preview.png`. The version number is your own file-management convention, not an automatic app feature. After saving, confirm that the files actually exist and are not unexpectedly zero bytes before moving on. ## 5. Check the result in the receiving application If you have the recipient's software, open the PSD and first compare its overall appearance with the preview. Then check layer count, order, visibility, and transparent edges. If you lack that environment, list these checks in the handoff notes and ask the recipient to confirm them rather than claiming full compatibility in advance. Pay particular attention to text, highlights, semitransparent edges, and overlapping colors. Applications may handle layers and colors differently, and a visual preview provides a clear reference. If you find a discrepancy, identify whether it comes from a layer's contents, compositing, or the display environment before deciding whether to deliver separate image layers instead. ## Final checks and handoff checklist A simple handoff can include a PSD, a preview from the same version, and a short note. State the artwork's pixel dimensions, whether it has a transparent background, which parts need further editing, and who retains the native artwork. Avoid unverifiable promises of lossless, complete compatibility with all software. If the recipient only needs the final composite, reduce unnecessary project files. More files do not make a handoff more professional; clear explanations of each file's purpose matter more. Keep your native version afterward so that you can resume from the correct state if revisions are requested. ## Why you still need the native artwork Aquarell's native format lets you return to the app and continue editing. Editable text, layer groups, and similar information should be retained in the native artwork; PSD is a way to exchange pixel layers. Save them separately to avoid discovering later that only rasterized content remains. Keeping the original also means retaining the relevant revision stage. If you continue editing after export, keep a clear version record rather than overwriting the delivered state beyond recovery. A folder or note saying “Delivered v03” can help you and the recipient stay aligned. ## Questions and limitations ### Why can I no longer edit the PSD text with a text tool? Aquarell exports PSD text as pixel-layer content. The text's appearance can remain as an image, but that does not imply it is editable text across applications. To change the wording, return to the native artwork or typeset it again in the receiving application. ### Are layer groups preserved in full? Do not assume so. The current interface explicitly states that editable text and layer groups remain in the native artwork. Plan the handoff around pixel layers and inspect the actual exported result. ### If the recipient sees different colors, does that immediately prove an export problem? No. First compare the file with the matching preview, then check the display environment and the software's handling. This tutorial does not involve cross-device color calibration or guarantee identical display in every application. ### Can I keep painting later if I save only the PSD? Whether you can continue editing with the same structure depends on import support and the information retained. Keep the Aquarell native file to reduce uncertainty, rather than relying solely on reimporting a PSD to restore every editing capability. ## Sources and applicable version Information checked on October 22, 2026, for Aquarell 1.0.5 (iOS / iPadOS 15.0 or later). See [the official description]() and [Apple release lookup](); the interface may change with the version. ## Keep practising - [Layer responsibilities]() - [Saving native versions]() - [A hand-drawn text card]()