Images and uploaded files
An asset is a file in the CMS media library. Its URL looks like
/api/assets/<id>/content, where <id> is Viking's generated identifier.
The same relative URL works in the authenticated CMS and in a published site,
because publication copies assets into the static release.
Upload and insert an image
- Open a page and use its image/media control to select a local file.
- Upload it to the media library and select the resulting image for insertion.
- Provide useful alternative text where the editor offers the image's attributes. Alternative text describes the image for readers who cannot see it.
- Preview, save the draft, and publish when it should be public.
Normal uploads allow PNG, JPEG (.jpg/.jpeg), GIF, WebP, AVIF, BMP and ICO,
and text documents (.txt/.json). The server checks content as well as the
filename. Renaming an unsupported file to .png does not convert it. The file
limit is 50 MiB; an ingress may enforce a smaller request limit. Reduce large
images before uploading if they make pages slow. Text documents download as
attachments rather than becoming executable page content.
SVG, HTML, JavaScript and CSS are rejected as normal media uploads. For a file that must be distributed unchanged, use a raw downloadable object which serves its bytes as an attachment. Theme images/fonts have separate packaging and size limits; see themes.
Reuse, replace and remove
Choose a site favicon
A favicon is the small image browsers show beside a site's page title in tabs and bookmarks. Upload an image using a page's media control, then open Settings → Site favicon and select it from the uploaded-image list. A square PNG (for example, 32 × 32 pixels) or ICO is recommended for browser compatibility. The selector shows a preview and excludes documents and raw downloads. It uses the existing upload; selecting a favicon does not add the image to page content.
Choose Save settings, then preview a page and Publish to update the live site. The favicon applies to every page, with or without a theme. Choosing None, saving and publishing removes the favicon link. Choose another image to replace it. Clear or replace the selection before deleting that image from the media library. Published releases and rollbacks retain their own favicon settings and bytes. Browser favicon caches can delay a visible change; try a fresh tab or reload after confirming the new publication is live.
Reuse or delete media
Reuse an existing library asset when several pages need the same image. In
Markdown source, insert the returned URL, for example
, replacing ASSET_ID with the
actual uploaded ID. An image path on your own computer is not a website URL.
Uploading a replacement creates another asset; update references to use the new URL, save, preview and publish. Existing releases keep their copied bytes. Remove a raw object's file/image references before deleting those assets; references in raw objects can cause an in-use conflict. Review ordinary page links too: do not assume deletion will rewrite every image/link in page source.
All uploaded assets are included in publication, not just files visibly used on a page. The media library is not a private file vault. Delete confidential uploads before publication; if they have already been published, contact your administrator about retained releases, backups and public/proxy caches.
External images and common failures
Images hosted elsewhere can disappear, change or fail inside the CMS's same-origin preview restrictions. Upload a permitted local copy if you have permission to use it. WordPress import offers guarded copying of public images; private-network media needs manual upload.
An unsupported-type error means use a supported format or a raw object; a size error means reduce the file or ask the administrator about proxy limits. If a public image is missing, check the saved URL and publish again. A file uploaded after the active release was built is not in that release.