LazPaint
LazPaint 7.3 is a lightweight cross-platform image editor built around bitmap and vector layers, selections, painting tools, color adjustments, filters and command-line processing.
What LazPaint does
LazPaint is a compact image editor for quick retouching, drawing, icons and layered graphics. It combines bitmap and vector layers with selection masks, painting tools, color adjustments, filters, textures and a command-line workflow.
Version and platform boundaries
Version 7.3 is available as Windows installers and portable archives, macOS packages, Linux packages and selected BSD builds. Choose the package for the actual CPU and operating system; a portable archive does not imply that every plugin or library is bundled.
Project files and exports
Keep an editable project with its layers, objects, brushes and color settings, then export a separate PNG, JPEG or other delivery copy. A flattened image does not preserve all editable layers or vector objects.
Script and batch safety
Python scripts, command-line actions and third-party effects may read or change local files. Review their parameters, use a dedicated input and output directory, and test them with copies before processing a large collection.
Maintenance note
Review date: 2026-08-23. The page was checked against LazPaint 7.3 package types, layered editing, high-DPI behavior, scripting boundaries and export verification.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave LazPaint to this cloud drive
Baidu Netdisk
Save LazPaint to this cloud drive
LazPaint 7.3 installation, layer editing and safe export guide
Select the package for the operating system and CPU, build a small layer workflow from a copy of an image, and keep the editable project separate from exported delivery files.
Before you start
- Prepare a disposable image with transparency, layers and a non-ASCII path, plus a backup of the original image, fonts and color settings.
- Match Windows, macOS, Linux or BSD architecture to the package name; do not mix libraries from another platform.
- If scripts or batch commands are needed, review their code and establish separate input, output and rollback directories.
Installation steps
- 01
Choose an installation or portable package
Use the 7.3 installer for regular Windows use, the matching ZIP for a portable test, DMG on macOS, and DEB, AppImage or a distribution package on Linux.
- 02
Check the first launch
Confirm that the canvas, toolbox, layers and color panels open correctly, then check interface scaling and language before importing a real project.
- 03
Create an editable test project
Open a test image, save a new project immediately, keep the background copy untouched and verify undo, transparency and layer order before editing.
Quick start
- 01
Make a local layer adjustment
Use a selection mask to limit the affected area and apply a curve, hue change or filter on a separate layer so the original remains available for comparison.
- 02
Check canvas and pixel dimensions
Distinguish canvas resizing from image resampling and inspect edges, transparent pixels and text at a one-to-one view before exporting.
- 03
Save the project and export a copy
Save the layered project first, export a PNG or JPEG with a new name, then reopen the result to verify dimensions, transparency, color and metadata.
Usage tips
- Layer effects, blending modes and vector objects may not transfer perfectly between editors; inspect each layer or flatten only a delivery copy.
- Undo history is not a version history. Use incremental project names and external backups for long editing sessions.
- Batch commands should specify an output directory and start with a small sample; wildcards and overwrite flags can affect many files at once.
Troubleshooting and uninstall
Why do layers, fonts or colors look different after opening a file?
Check whether the format preserves those features, then inspect missing fonts, color profiles and blending modes. Export a compatibility copy or rasterize selected layers without overwriting the original project.
Why will an AppImage, portable package or macOS build not launch?
Confirm the architecture and package integrity, grant execution permission to an AppImage for the current user, and review the operating system security message. Use a matching build rather than replacing libraries at random.
- Preserve projects and presetsSave editable projects, brushes, colors, scripts and settings outside the application directory, and confirm that exported files are readable.
- Remove the package by its installation methodUninstall the system package, remove the macOS application or delete the portable directory after closing LazPaint; remove user settings only after checking that they are no longer needed.
Frequently asked questions
Is LazPaint a replacement for a full professional design suite?
It is well suited to lightweight drawing, layered retouching, icons and quick assets. Large publishing workflows, team asset management and specialized plugin pipelines should be tested with representative files before migration.
Why can a PNG export no longer edit the original layers?
PNG normally stores a composed bitmap rather than the complete LazPaint layer and vector structure. Keep the editable project and export a separate delivery image.
Can a LazPaint script be run without checking it?
No. A script can read or modify local files. Review its code and parameters, use a copy and run it with ordinary user permissions before applying it to a collection.