Teams that rent a remote Mac through MacPng often ship the same artifact twice: once as a clean master from Figma, and again as a client-safe PNG with a visible mark, integrity proof, and an auditable bundle. This article is a copy-paste friendly playbook—directory layout, a Bash + ImageMagick batch template, SHA-256 manifests, dated archives, and how to hang the whole flow off OpenClaw (Gateway + skills) with JSONL logs and retries. Pair it with the OpenClaw install guide (all platforms), the Figma/Sketch PNG export checklist, and watch folders: retries & log archive so permissions and backoff rules stay consistent across every pipeline you run on Apple Silicon.
Table of Contents
Export directory conventions & permissions
Figma’s desktop app writes wherever the designer picks; for automation, freeze one absolute path per campaign (or symlink a friendly alias). On the remote Mac, keep all automation under a single POSIX user—the same account that owns SSH sessions, LaunchAgents, and OpenClaw workers—so TCC prompts and file locks stay predictable.
Recommended tree (rename the root, keep the semantics):
~/FigmaDelivery/inbox— Figma “Export” target; watchers observe only this folder (flat is easier than deep trees).~/FigmaDelivery/staging— files move here atomically before watermarking so half-written exports never composite.~/FigmaDelivery/watermarked— final PNGs promoted after checksum + QA gates.~/FigmaDelivery/archive— immutable tarballs and copied manifests per release.~/FigmaDelivery/failed— inputs plus JSON sidecars describing the fault.~/FigmaDelivery/logs— append-only JSONL (one line per stage).
Permission checklist: (1) chmod 750 on the root; never use 777 on shared hosts. (2) In launchd plists, pass HOME and absolute paths—tilde expansion is unreliable. (3) Install ImageMagick where the worker resolves it (brew install imagemagick is typical). (4) If exports land on a network volume, test lock latency; slow SMB can defeat naive “stable size” checks—increase debounce or copy to local SSD first. For export quality baselines (sRGB, alpha, scale), align Figma presets with Figma vs Sketch transparency comparison before you burn marks on the wrong master.
Watermark parameters: position, transparency & safe zone
A production watermark is a contract: legal wants the mark readable; brand wants it subtle; product design wants critical UI and faces outside a safe zone. Encode those rules as constants next to your script, not as one-off clicks.
Asset: use a transparent PNG mark (RGBA) at 2× the largest width you expect to composite—ImageMagick will scale down cleanly. Avoid SVG-to-raster inside the hot path unless cached; for SVG masters see SVG → Retina PNG matrix.
Geometry table (tune per brand; values are starting points):
| Parameter | Typical value | Notes |
|---|---|---|
| Gravity | SouthEast or SouthWest |
Corner placement reads clearly on thumbnails; alternate corners per locale if mirroring UI. |
| Edge inset (safe margin) | 24–48 px at 1× |
Scale with % geometry for ultra-wide banners: e.g. -geometry +5%+5% after defining reference width. |
| Opacity / dissolve | 30–45% visual |
Use -dissolve 35 (percent) or alpha multiply; verify on both light and dark hero backgrounds. |
| Safe zone (content) | Lower-right quadrant margin | For campaign art with faces, switch to NorthEast or add a second pass that rejects compositions overlapping a bounding box (optional OpenCV step). |
Single-file composite template (ImageMagick v7 syntax; adjust paths):
MAGICK_WATERMARK="$HOME/FigmaDelivery/assets/mark_rgba.png"
IN="$1"
OUT="$2"
magick "$IN" "$MAGICK_WATERMARK" -gravity SouthEast -geometry +32+32 \
-compose dissolve -define compose:args=35 -composite "$OUT"Batch every *.png in staging/ inside a loop; log stage=composite with duration. After watermarking, optional lossless byte shrink belongs in a separate stage—see PNG metadata & lossless recompress—so you never strip ICC before the client signs off.
Checksum manifest & version archive
Checksums turn a folder of PNGs into an evidence bundle: ops can prove what left the remote host, and you can re-run QA months later without guessing bytes.
Manifest checklist:
- Per file: relative path,
sha256, byte size,mtime(UTC ISO), optional Figma file key from parent folder name. - Per job:
job_id(UUID),pipeline_version(semver of your script),watermark_asset_sha256,git_shaif the repo defines presets. - Promotion rule: append one JSON line to
manifest.jsonlonly after composite + optional PNG QA gates pass.
Checksum one tree:
(cd "$WATERMARKED_DIR" && find . -name '*.png' -print0 | \
sort -z | xargs -0 shasum -a 256) > "$ARCHIVE_DIR/manifest-${JOB_ID}.sha256"Version archive: after a successful batch, create archive/drop_YYYYMMDDThhmmssZ_${GIT_SHORT:-local}.tar.gz containing watermarked/ and the manifest. Store the same tarball name in your ticket system. If you need differential delivery, also emit a manifest.jsonl consumed by CMS importers—same schema your CLI chain article uses for handoff files.
OpenClaw triggers & log backhaul
OpenClaw should orchestrate, not re-implement ImageMagick. Treat your Bash (or Python) entrypoint as the single source of truth for exit codes; Gateway or a registered skill only schedules it and captures stdout/stderr.
Trigger options:
- Folder watch → task:
fswatch(or your OpenClaw watch integration) emits paths; debounce and enqueue a job record. - Skill invocation: expose
figma_png_watermark.runwith parameters{ "inbox": "...", "mark": "...", "campaign": "..." }; validate paths against an allow-list to prevent arbitrary shell. - Scheduled slice: for nightly bundles, use
launchdto call OpenClaw CLI with a frozen config—easier capacity planning than pure events.
Log backhaul: every stage writes one JSON line: {"ts":"...","job_id":"...","stage":"move|composite|sha256|archive","path":"...","exit":0,"ms":124}. Tail these files into your observability stack, or add a tiny webhook POST from OpenClaw after each job—keep payloads small. For skill packaging patterns, cross-read OpenClaw self-evolution & skills and local knowledge base so prompts and runbooks stay versioned next to the script.
Retry template: on exit!=0 classify stderr: “resource busy” / “disk full” → exponential backoff (5 s, 20 s, 60 s) up to three attempts; “corrupt image” / policy violation → move to failed/ immediately. Mirror the backoff narrative in watch/retry HowTo so operators have one runbook.
Common failure FAQ
Q: Composite succeeds but colors look washed out versus Figma.
A: Confirm export and composite both assume sRGB; avoid accidental CMYK marks. Re-read PNG color management (sRGB vs P3) before changing profiles mid-pipeline.
Q: Same PNG processed twice gets double watermarks.
A: Use an idempotency key: move originals out of inbox into staging with mv, or maintain a small SQLite/JSON cache of inode+mtime. OpenClaw should pass job_id into the env so replays are traceable.
Q: Gateway shows success but the archive tarball is empty.
A: Usually a relative-path bug when tarring—always cd into the parent of watermarked/ or pass absolute paths to tar. Log directory listings at stage=archive.
Q: Performance collapses on 4K frames.
A: Cap parallel magick workers using the queue slicing advice from 4K PNG batch export on remote Mac; watermark is memory-bandwidth sensitive.
Q: Legal wants IPTC copyright after the mark.
A: Chain a second stage with exiftool as in IPTC metadata watch steps; keep watermark first so pixel review matches delivered bytes.
In short, a remote Mac is the right place to park Figma-driven PNG delivery: stable paths, native ImageMagick, and headroom for checksum + archive steps that laptops resent. When your manifest, tarball, and JSONL logs line up, client QA stops debating “which attachment was final” and starts signing the bundle hash. If you are standardizing several OpenClaw jobs, reuse the same directory vocabulary across multi-size PNG watch folders and this watermark flow so one on-call runbook covers every campaign.
Rent a Remote Mac for Overnight Figma PNG Pipelines
You can open the MacPng homepage, review rental packages and pricing & nodes, and read the SSH/VNC setup guide without creating an account (limited-time in-site access). Pick a node, attach your worker, and deploy this HowTo unchanged—same folders, same checksum contract, same OpenClaw hooks.