PhotoCraft layers and masks: a beginner guide

Layers separate the pieces

Think of a layer as one piece of the image stack. A background photo, a painted mark and a text element can live separately. Reordering changes what covers what; visibility and opacity let you compare changes without immediately removing content.

Masks control where an edit appears

A pixel mask controls visibility using values from hidden to visible, with intermediate values for partial transparency. It can hide part of a layer without erasing the underlying pixels. An adjustment layer changes appearance and can have a mask that limits where the adjustment applies.

Preserve the editable stack

Keep a layered project copy before exporting. PNG and JPEG outputs normally flatten the visible result and do not retain the editable layer stack. For PSD exchange, reopen a copy in the destination application and compare it; masks and effects do not imply perfect interoperability.

Begin with a document you can inspect

Use a small duplicate image rather than a client design for your first layer exercise. Download the synthetic sample linked from the PNG workflow and keep the untouched original. Open it in the actual editor and identify the active document and layers panel. A panel label describes an interface concept; it is not proof that every Photoshop layer type can be imported or exchanged without change.

The website hosts PhotoCraft v0.12.0, an early-alpha browser build. Its interface is English and its behavior can differ from a newer native release. This guide explains how to reason about layers and verify a workflow. Our published simple brush-and-PSD test does not exercise a multilayer mask document, so it must not be read as a mask-compatibility benchmark.

Separate the visible image from its structure

The visible canvas is a composite of the document. Layers can let an application keep parts separate so you can change one element without permanently changing another. A flattened export records an appearance, while an editable document is intended to retain more structure. These roles matter when you decide which file to send to a recipient.

Start by recording the existing layers and their order. If the layer menu in your running build offers the operation you need, create a separate test layer and name it descriptively. Paint an obvious mark there, then toggle that layer's visibility. The expected observation is that your mark disappears and returns without changing the original content. If you cannot obtain that behavior, record the operation as unsuccessful rather than continuing under a false assumption.

Test one operation at a time

For each operation available in your version, make a small change and inspect the result before proceeding. Check which layer is selected before painting. If a stroke seems to disappear, first inspect visibility, selection and whether the document is showing the intended layer. Changing several controls at once makes it harder to identify the cause.

Try a reversible change before any destructive merge or flatten command. Save a checkpoint first and keep the original. Undo history belongs to the live session; it is not a backup you can rely on after reloading. Use the saving guide to create a working file and a reference PNG at the points where losing the current state would matter.

Understand what a mask is meant to do

A mask is commonly used to control which parts of a layer contribute to the composite. It is different from deleting pixels outright. In an application that supports the relevant mask operation, you should be able to alter the visible contribution while retaining the underlying image. The precise controls and supported mask types depend on the running software.

Do not assume PhotoCraft's behavior from a Photoshop tutorial. Inspect the menus and upstream documentation for v0.12.0, then use a synthetic example to test the exact operation. We have not published a controlled test proving all mask creation, import and round-trip behaviors. If the required command is missing or the result changes on reopening, preserve that observation and use a workflow verified for your needs.

Check edges and transparency outside the canvas

A checkerboard display can help indicate transparency, but it is not the final delivered file. Export a PNG and open it in a viewer that can show transparency against contrasting backgrounds. Look for edge artifacts, unwanted opaque areas and an unexpected crop or size. A screenshot of the application includes interface scaling and should not replace inspection of the downloaded image.

For a handoff, explain whether transparency is intentional. A recipient viewing the image against white may overlook an unwanted edge that appears against dark content. Keep a reference that makes the intended result clear. This is a visual quality check, not a promise that all underlying masks remain editable in another program.

Reopen before trusting an editable save

Save a new PSD checkpoint, reopen it and compare both the composite and the required layer structure. Check names, order, visibility and the particular elements the recipient needs to edit. A file that opens is not automatically a successful handoff. Conversely, one unsupported feature does not mean every other part of the document failed.

Our PSD guide includes a small downloadable sample and explains its limits. Your layered mask example needs its own result record. If the recipient uses Photoshop, reopen it there as part of acceptance or label that step unverified. If structure cannot be preserved, agree on a flattened output only when it actually meets the recipient's task, and retain the original editable source separately.

Keep a useful troubleshooting record

Describe the input, chosen layer, operation, expected appearance and observed output. Include a sanitized screenshot and the software version. Use a minimal reproduction with no private artwork if you need to report the behavior upstream. A statement such as “the second layer disappears after reopening this sample” is more actionable than “layers are broken.”

The practical goal is control over what changes and a saved result you can verify. If you cannot establish that control in the pinned version, do not experiment on the only copy of important work. Keep originals, save checkpoints and use an established tool for any required feature that remains unverified.