Start with a document you can keep editing
PRVKIT Editor brings photographs, text and supported layered artwork into one browser workspace. Use it for a poster with editable headings, a product composition, a crop that needs a precise selection, or a supported PSD whose individual layers matter. A flattened image export and an editable project serve different purposes: keep the project when you expect to revise the work, and create a separate delivery image when the design is ready.
The workspace starts dark. A light theme is an explicit choice in settings. Open a local file or create a document from a preset or custom dimensions; there is no requirement to upload creative files to a processing service. External image URL import is unavailable in this release configuration. If an image is online, obtain a permitted local copy and open that file instead.
Build the design around layers
Put elements that need independent changes on separate layers. A photograph, a shape behind a caption and a Type layer above it can then be selected, moved and revised without repainting everything together. Layer order determines which objects cover others. Visibility, opacity and supported blend settings offer different ways to combine them; inspect the composite whenever you change those relationships.
Selections limit where an edit applies. Before painting, erasing or applying an adjustment, check both the selected layer and the selection boundary. A result that appears to do nothing may be constrained by an active selection or directed at a hidden layer. Undo reverses document edits, but a downloaded original remains your independent starting point. Do not treat a long history as a substitute for saving.
Type stays editable where the imported or newly created text maps to the supported Type model. Select the Type layer, enter its text and inspect the font, spacing and alignment before finishing. Missing or substituted fonts can change line endings and layout. A matching filename or familiar font name does not establish that the exact font is installed or licensed for your use.
PSD support has a defined boundary
Supported PSD work is Free; PRO is not a promise of broader Photoshop fidelity. RGB8 imports can retain raster layers, groups, supported affine point or paragraph Type and raster masks. More complex Photoshop constructs may be preserved, approximated, rasterized or unavailable. Read the compatibility information rather than assuming that a recognizable composite means every original feature is editable.
The RGB16 path retains original source samples separately from its display preview. Compatible text can be edited, and precision-safe PSD saving supports the verified flat, normal-layer subset. Pixel painting and unsupported high-depth constructs remain protected. This is not a general 16-bit Photoshop replacement, nor a guarantee that every adjustment, group effect or color profile can be changed and round-tripped without loss. RGB32 has narrower precision-retention behavior.
For a client PSD, first compare the initial appearance, layer list and important text with the source application. Make a small intended change, save a new file and reopen it in the application that will receive it. Keep the original PSD throughout. Exporting a PNG composite is useful for visual review, but it cannot prove preservation of the PSD's editable structures or high-depth samples.
Choose the right kind of import
PNG, JPEG and still WebP become raster content. Supported SVG shapes, paths and simple text use a restricted vector subset; scripts and external resources are refused. PDF import renders a selected page to a raster layer. Its text and drawing objects do not become separate editable Editor objects. PDF-compatible Illustrator import follows that page-rendering model and requires the relevant PRO access.
Additional PRO adapters cover bounded OpenRaster, Sketch, Krita, TIFF and Procreate workflows. They have different fidelity rules. Procreate recovery may reconstruct supported paint layers or provide a preview; it does not create a native Procreate editing session. Editor HEIC/HEIF import depends on the browser's native decoder and has no bundled fallback. The shared HEIC conversion tools have a separate decoder path; their availability does not expand the Editor adapter.
Use the support table for format-specific ceilings. The canvas limit is 8,192 pixels per side, but a file below that edge limit can still exceed a decoded-pixel or working-memory budget. Compressed file size alone is a poor estimate of how much memory layered artwork needs. A refused import is not permission to rename its extension or bypass the admission checks.
Save for the next person and the next session
Save Project downloads an editable .prvkit document. Image exports such as PNG, JPEG and WebP are composites; supported PSD and SVG exports serve narrower interchange needs. PRO OpenRaster export retains the supported layered raster representation, with text and effects baked where required. Choose the format according to what the recipient actually needs to change, not only what they can open.
Optional PRO Local Recovery stores checkpoints in this browser when enabled. It is device-local storage, not a cloud backup or a permanent guarantee. Browser cleanup, private browsing, quota pressure or a different profile can make it unavailable. Download a project before closing important work, changing browser profiles or following a workflow that might replace the active document.
After export, open the actual downloaded file. Check dimensions, transparency, font appearance, edges and the changes you intended. For an editable deliverable, check editability as well as appearance. A successful download request does not establish that a file has finished saving to disk.
Keep the privacy claim practical
Creative processing stays in the browser, while the site still downloads code, fonts and optional processing assets. Account and entitlement information is a separate system. Local processing does not protect a shared or compromised device from extensions, other users or exposed downloads. Use the existing File Privacy explanation when deciding how to handle sensitive work, and keep source files and delivery copies clearly separated.