Lightweight preview SVG: a screen-grade snapshot split from print masters and production slices
`flatten-psd-svg-preview` targets “you can read the layout and hierarchy” rather than press-ready fidelity: resolution often sits below print DPI and bleed marks stay out. It belongs in Slack-ready docs or Jira attachments, not on a plating ticket. If procurement only sees the preview link, the plant should refuse the job—pair it with explicit print exports.
使用方法
- Build a PREVIEW layer comp in Photoshop that hides millimeter crop marks and keeps only what reviewers must see, then merge and upload.
- Embed once inside the real review tool; confirm it is not auto-flattened to JPEG and losing the SVG shell. If the tool rejects SVG, export PNG instead of forcing unsupported fields.
- Write decisions in the ticket with file hashes; chat screenshots are hints only, and arguments settle against archived SVG plus PSD.
PSD to SVG (preview) FAQ
We only ship a flattened preview SVG—how do we contractually separate it from the PSD print master so buyers do not send it to press?
Label tickets and filenames preview-only: the SVG aligns teams on layout, not separations, bleed, spot inks, or ICC for press. Version the print PSD or PDF/TIFF package on its own path with approvals. If a vendor receives only the preview URL, refusal is correct—the converter is not responsible for procurement skipping the mechanical bundle.
Body copy looks soft in the web preview—does that predict a fuzzy print run, or are the two acceptance channels measuring different DPI budgets?
Preview long edges often bake at screen-class resolution while print may require 300 dpi vectors or high-line halftone rasters; spell minimum type sizes and knockout rules in the print spec. Soft type in-browser usually means insufficient preview pixels or aggressive browser scaling, not a verdict on plates until you export the merged frame at print dimensions.
Transparent edges show white or colored halos in the SVG—Photoshop matte, PNG export, or the review page background?
Most halos come from merging against a different matte than the page background plus premultiplied-alpha compositing differences. Lock the preview export background to brand light/dark grays in PS and QA both mats in the spec; arguing in chat without a same-background PNG diff wastes days.
Our review SaaS rejects SVG so PMs paste screenshots—do we lose audit evidence?
Treat screenshots as conversational garnish only; the system of record must store download URLs, SHA256, and upload timestamps. Disputes resolve against object-storage SVG/PSD artifacts. Add a mandatory hash field to tickets so sign-off cannot rely on a blurry Slack capture six months later.
Multi-artboard PSDs in batch—will we silently export the wrong board if visibility recipes drift?
Flattening honors whatever layers are visible for the chosen artboard; freeze action sets and naming prefixes before automation. Split queues per campaign aspect family so a rogue default visibility script does not leak draft layers into customer-facing previews.