The current development image workflow keeps your original photo and saves each placement’s composition separately. The Astro layer is not published on npm yet; see the Astro layer for its development status.
Edit a placement
- Open a Siteboard in Content mode and select an image.
- Upload a still JPEG, PNG or WebP, then choose Edit image.
- Choose Focal point to keep a subject in view, or Crop to select a region. Numeric controls are available alongside pointer, touch and keyboard controls.
- Choose a breakpoint when the composition should change at a different width. Settings inherit until you edit them; Remove override restores inheritance.
- Choose Apply to save one undoable change. Cancel and Escape discard it.
A second placement can use the same original with different settings. Replacing an original resets that placement’s composition and keeps its alternative text. Old preview-only references remain displayable; import an original to crop them. SVG references retain their preview workflow.
Originals are limited to 8 MiB, 16 megapixels and 8192 pixels per side. Small crops reduce usable resolution. Output widths stop at the available source pixels.
Native source projects
Select a native image connected directly to a declared image field and choose
Replace image in the Content toolbar or inspector. A plain image replacement
keeps its existing markup, dimensions and alternative text. Desktop imports the
original under public/images/blockbite/ and updates that section’s content value;
it does not require the managed crop service. Undo restores the previous value.
Advanced cropping uses the optional managed Astro image component. Desktop can
explicitly adopt a supported plain image through Enable cropping. It
updates the island, its page call and the page’s crop metadata together. A fixed
or unsupported crop frame can still allow ordinary image replacement. Dynamic or
ambiguous sources, image srcset and picture sources remain unavailable for
automatic replacement. Images without a supported field connection explain the
next step in the inspector.
The project’s native aspect ratio owns the frame. A fixed height or ambiguous frame needs source work before cropping. Existing projects must explicitly configure the managed image service; Desktop preserves a custom image service. Generated projects configure it when needed.
Native dev, Play and static builds use Astro’s image generation and deliver
ordinary picture, source and img elements. Image-editor code stays in the
editor. Managed crop output for SSR, external image services, WordPress and EmDash
is not supported yet and reports an error before exporting a wrong composition.
Save, transfer and share
Local editing keeps original files with the board or selected project. A capable hosted server can save originals privately and publish cropped display images. Revoking an original removes access to its hosted derivatives. Hosted display currently accepts unprofiled and supported sRGB images; other embedded color profiles require a converted copy. The retained original remains intact.
Source review shows the saved crops. Crop and replacement proposals for those managed fields stay in Desktop.
Use a complete backup when moving originals into a new board. Backups support up to 32 originals, 32 MiB of decoded originals and a 48 MiB file. A clipboard paste that cannot find its original refuses the change and directs you to a backup. Cloud source bundles have separate size limits and refuse oversized originals.