Before you begin
- PNG supports transparency; JPG does not.
- Pixel dimensions and DPI-derived scale are different ways to set raster output.
- Page fit and outside-page objects can affect exported bounds.
- A preview does not verify the editability of the CDR master.
Define the export specification
Manual processing suits a small set or a rule that has not been tested yet.
- Open a representative CDR file.
- Check the page boundary and visible artwork.
- Export a PNG at the intended size and transparency setting.
- Inspect it at actual pixel size before repeating the settings.
Quality checks before delivery
Open representative outputs and review the actual vector or raster file at the size and in the application that matters.
- Exact pixel dimensions
- Transparent versus solid background
- Anti-aliased edges
- Cropping and visible artwork bounds
Troubleshooting
Keep the source unchanged while you diagnose a failed file. Other files in the batch can continue.
- If transparency is unavailable, confirm PNG is selected.
- If content is cropped or padded, inspect page fit and outside objects in the source.
- If outputs need different sizes, create separate source groups or runs.
Workflow
Batch workflow in AZTER
Start the batch after grouping the source files and defining the output.
- 01
Group CDR files that need the same raster output.
- 02
Choose Export Preview in AZTER.
- 03
Select PNG, set long-edge pixels or DPI-derived scale, and enable transparency if needed.
- 04
Choose a separate output folder and run the batch.
- 05
Check pixel dimensions, background, and edge quality.
FAQ
Frequently asked questions
Should I test every batch on a small set first?
Yes. Use representative files, including at least one difficult example, before applying one rule to a large folder.
Does AZTER change the source files?
No. AZTER uses separate source and output folders. If an output name already exists, AZTER adds a number. It replaces an existing file only when you enable Overwrite.
What happens if one file fails?
The failure is reported and ordinary per-file failures do not stop the rest of the batch. Review the completion summary and handle the exception separately.