Export and troubleshooting

Save native Aquarell projects: keep drafts, finished work and shared images separate

Use clear filenames and three checks to retain editable Aquarell projects, rather than treating a finished PNG or PSD as the only original.

English translation of the Chinese original, translated on . 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.

A sharing image lets others see the work; a native file lets you continue editing it. Aquarell exports native artwork as well as PNG, JPEG, and PSD. Giving each format a clear purpose reduces the problem of having an image but no longer being able to edit its layers or text.

This guide establishes a simple archive workflow for personal-blog artwork: keep key stages, export a native document, confirm it works, and generate a publication copy. It requires no extra subscription and does not assume the app automatically backs up your work to the cloud.

1. Decide which stages deserve a saved copy

For a small exercise, keeping the finished native document may be enough. For a card requiring repeated revisions, save copies at sketch approval, coloring completion, and final text. Choose stages according to the risk of later changes; you do not need a new file for every stroke.

For example, leaf-card-sketch, leaf-card-color, leaf-card-final-v01 describes both content and stage. Avoid ambiguous names such as “New Artwork 1” or “Final Final.” Dates help sorting but cannot replace a description of the artwork.

2. Choose the native-document option in Export

After an important stage, open Export and select the native-document option. Its label may mention Aquarell, artwork, or a native file; some inherited English names may differ. Follow the actual format description.

Use the system share sheet to save to a known location, such as a dedicated project folder in Files. Return there and confirm the file exists before continuing. A closed share sheet alone does not prove that saving succeeded.

If the system asks for a destination, check the folder carefully so you do not save into a temporary location that is hard to find later. External drives, cloud storage, and local folders have different availability requirements; choose for your own device setup.

3. Name originals and publication files separately

Use a common prefix for files from the same stage: the native document is leaf-card-v02, the preview is leaf-card-v02-preview.png, and the blog output is leaf-card-v02-blog.jpg. The extension comes from the actual exported format. Do not rename an image to give it a native-document extension.

If a filename conflict appears, decide whether you really intend to overwrite. Versioned files should usually keep the old copy and use a new name. Do not delete an older file merely to tidy the folder when it may be your only usable artwork. Verify the new file first, then remove only copies you know you no longer need.

4. Check editability using a copy

After finishing important work, reopen or import a dedicated exported test copy using the current version's import workflow. Check canvas dimensions, major layers, and text appearance to confirm that it matches the stage you saved.

If import might affect your library, note the original filename and avoid experimenting on the only original. You need not change the artwork to inspect it: check layers, open the text controls, and exit. For an editing test, use a separate copy clearly labeled as a test.

The check is not a compatibility guarantee for every future version. It helps detect a problem with this particular export or save. If an error occurs, retain the original and the error details rather than repeatedly overwriting the same path.

5. Make the second copy genuinely independent

Copy important work to another dependable location, such as another drive or a cloud service you manage. Two shortcuts pointing to one temporary folder do not provide the same protection.

A filename in cloud storage does not necessarily mean uploading or local downloading has finished. Before switching devices, check synchronization status and actual file access. These are system or storage-service capabilities, not a claim that Aquarell provides automatic cross-device synchronization.

Completion checks and finding files later

Check at least three things: the file exists and has a plausible size; its name identifies a particular stage; and important files have been opened once to verify them. Keep publication images separately so you do not accidentally upload a large working document to the blog.

Record the final version, publication date, and matching filename in your notes. When revising a blog image, find the published version first and save a new iteration. This avoids guessing from thumbnails or overwriting a previously delivered file just to change a heading.

When to organize older versions

Verify the new version before deciding which older ones to keep. Sketches, pre-color-change versions, and the published final often have different recovery value. Repeated copies with no meaningful changes can be organized after checking them.

Organize only files you clearly recognize; do not bulk-delete a directory based on vague names. If the original will not open but its preview remains, the preview at least preserves the visible result. Keeping related files while investigating gives you a better chance of recovery than hurried cleanup.

Questions and limitations

Why keep a native document if I already have a PNG?

PNG is a flattened display image and does not retain all of a native document's editing structure. Use the native document if you will later edit the sketch, color, text, or layers separately.

Can PSD completely replace the native format?

Do not assume so. Aquarell exports a pixel-layer PSD; editable text and layer groups should still be retained in the native document. PSD exchanges some content but is not an equivalent copy of every piece of information.

Can I delete the local original once it is in cloud storage?

First confirm that uploading has finished and actually open the file from the destination. Then decide according to your storage plan. This guide does not guarantee any cloud service's synchronization, and a visible filename alone is not a reason to delete your only usable original.

What if an old file will not open after an update?

Preserve the original bytes rather than repeatedly rewriting the file in other programs. Record the app version, file source, and exact error, then contact app support. Compatibility must be checked in practice; changing an extension cannot repair it.

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