The short answer
Use “Save project” before closing an Image Studio design you will revise. Download a separate finished image for its destination. Later, use “Open project” for editable elements; opening the PNG instead gives you its saved pixels. Keep clear names for both files.
Open the free toolDecide which file serves the next person
A design can have two useful outputs. The finished image is for a slide, website or message. The editable project is for changing the wording, layer positions and other working choices. Do not expect the same file to serve both purposes automatically. An image can look exactly right while providing no separate text box for next month’s date.
Consider an illustrative community workshop card. Today it says “Repair afternoon” with one date; next month the room and time change. The person publishing today’s card usually needs only the checked image. The person preparing the next version needs the project. These are example roles, not a collaboration feature that automatically shares your workspace. Agree on the handover and keep both files identified in your own folders.
Keep separate text and shapes while editing
In Image Studio, click an element to select it and double-click text to edit its words. Check the selection before changing a font, effect or size. Separate a frequently changed date from a main title when it makes revisions clearer. Combining every word into one element can create unnecessary work when only a small part changes.
Use the layer controls to identify the right element, particularly when shapes or text overlap. A hidden selection error can change a decorative label rather than the intended heading. If an edit goes wrong during the session, “Undo” can help. Inspect the result before continuing with several further changes. The aim is an understandable working structure, not the largest possible number of elements. A modest card with clearly separated roles is easier to revise than one whose selected object is always ambiguous.
Save a project at a meaningful checkpoint
Use “Save project” after a stage you would want to recover. Confirm that the browser saved the project download and give it a useful name without replacing its file extension. Keep a copy of an approved version before exploring a different crop or color arrangement. A second project is a concrete checkpoint; a memory of how the preview looked is not.
The project contains the original image and editing information, including working layers and the current composition. It is the tool’s own JSON format, not an ordinary photo and not a generic JSON document accepted from any application. The original material can make the project much heavier than the final image. Read any size-limit error and keep the current source files available rather than assuming every project size can be saved.
Export a finished picture deliberately
Choose the image format needed by the destination and create the output. PNG supports transparent pixels; JPG needs a solid appearance instead. WebP is another option when accepted. None of those finished image exports turns the separate text elements into editable project layers for a later Image Studio session. The letters become part of the displayed image.
Check the actual saved export after downloading. Review line breaks, missing characters, cropping and any edge that depends on transparency. If the destination has a file-weight ceiling, examine that too. A correct project save does not establish that the exported picture meets a portal’s requirements. Conversely, a small usable PNG does not confirm that the editable project has been backed up. Treat them as two checkpoints with different success conditions.
Reopen the project rather than the image
When revising, choose “Open project” and select the genuine saved project. After it loads, select the date or another text element and confirm that the expected edit controls are available. Opening the finished image through the ordinary image picker is a different operation. The visible words may be identical, but they are now pixels in a single picture rather than the original editable element.
Reopening a project is also different from restoring the entire old undo history. The implementation starts a new history from the opened state; do not promise a collaborator that every previous experiment can be stepped through. Keep separate checkpoints if an earlier layout might be needed. A project preserves its saved state, not every decision you made before saving. Test the edit you need before deleting or reorganizing any previous working copy.
Understand the original material in a project
The saved project embeds the source image and can retain its hidden metadata. A finished pixel-based export is a different handover. If a publishing collaborator needs only the illustration, send the checked final file rather than the entire source by habit. Consider visible personal information in both versions; rewriting image metadata does not remove a name printed in the design.
Fonts and other program resources may load from the website when needed. That is separate from uploading your photograph. Processing stays in the browser, but this does not replace your own file organization. Keep source, working project and approved export in places you control. Avoid several unrelated files all named final, especially when a date is the only change between two nearly identical event cards.
Handle a failed opening without losing the reference
If the project is rejected, read the message and verify that you selected the tool’s project rather than the PNG or another JSON. Renaming a picture to .json does not create a project. Return to a preserved copy before manually changing unfamiliar file contents. A partial or damaged file may need the original source and a new reconstruction of the design; this guide cannot promise recovery from every lost project.
For a simple verification, open a copied project, select a text element and make a harmless temporary wording change. Then discard that experimental version or save it with a distinct name. This is a suggested check of your own saved work, not a claim that every project has been tested. Once the project and final export are both identifiable and usable, the next person knows which file to publish and which file to edit.
Questions you might still have
Does transparent PNG mean editable text?
No. Transparency and separate editable elements are different properties.
Which command saves future editability?
Use “Save project” and retain its genuine project file.
Will reopening bring back every undo step?
No. The project opens at its saved state with a new history, not the full previous session.
Can I rename an image as JSON to edit its words?
No. An extension change does not reconstruct layers or create the required project data.
Does the project contain my source photo?
Yes. It can also retain source metadata, so consider that before sharing.
Which file should go to a publisher?
Usually the verified finished image. Send a project when continued editing is actually needed.
Sources & useful details
These guides are written from the current LoschaZ tools and the sources listed above. Examples are illustrations, not tests on every device or promises of an identical result.
