Confluence embeds: macro width, theme chrome, and attachment versions make the same JPG look like a different picture per skin
`confluence-visio-jpg` covers architecture or flow previews inside page bodies. Confluence responsively scales images and paints theme backgrounds, so white-matte JPGs may glare on dark skins or fake “white halos.” Preview in a sandbox space that matches production theming, and add copy that the raster is illustrative only and the .vsdx attachment is authoritative so readers do not treat compression artifacts as topology changes.
Confluence workflow: measure editor column width and theme colors, export a width-matched JPG, upload attachments, and log the page revision id
- On a test page insert the same macros as production and measure usable content pixels; export to that width so you do not upload a huge file that the UI only downscales—wasting bandwidth and exaggerating blocking.
- Screenshot full pages under default and dark themes; if dark mode fails acceptance, export gray-matte JPGs for dark or wire two attachment variants the theme can swap.
- Upload the controlled .vsdx beside the JPG and document both version labels in the change summary; audit comments should cite page revision numbers, not chat screenshots.
VSDX to JPG (Confluence) FAQ: responsive scaling, light/dark themes, paired attachments, revision traceability
After insert the image is squeezed to a narrow column and text is mush—is that export resolution or macro column width, and who owns the fix?
Usually width mismatch: export to the column width or provide a zoomable link; sometimes split into two stacked medium-width figures instead of one ultra-wide panorama.
PDF or HTML exports blur embedded JPGs compared to online reading—how do we align pipelines?
Export paths may recompress; feed the same canonical image URL or raise embedded DPI in the exporter—validate the exported artifact, not the editor preview alone.
Page history shows a JPG replaced under the same attachment name—how do readers know which revision they saw, and what must change notes include?
Bump attachment versions or rename with date/hash stamps and summarize at the page top; silent same-name overwrites destroy audit trails.
Lazy-loaded macros flash placeholders—should we shrink JPG bytes or split a small above-the-fold hero from a lazy high-res body?
You can lower quality if readability holds, add progressive placeholders, or split hero vs detail assets when flicker still harms reading.
Copying pages across spaces leaves image links pointing at the old space and breaks permissions—what must a launch checklist enforce?
After copy, verify attachments migrated with the page or switch to relative references; add a “cross-space link patrol” item to the release checklist.