Modules

Understanding compositions

Both formats support previews, accent colours, images, multiple embeds and expanding, copying, removing and reordering embeds. V1 uses fixed Discord fields, while V2 uses freely arranged blocks. The following sections explain the available inputs and their differences.

The name of a composition is only used for management in the dashboard and is not sent to Discord. Up to 50 compositions with names of a maximum of 50 characters each can be stored per server.

Components V1 / V2

New compositions start with V2.

Choose V1 or V2 before the first save. After saving, the version is permanent, including drafts and after removing a publication. Create a new composition to use another format. Duplicating preserves the version. Saved V1 messages are not automatically converted or deleted.

V1

V1 uses classic Discord embeds with an accent colour and fixed sections. Up to ten embeds are supported. The table gives maximum character counts. Author, title, description, footer and every field name and value together may contain at most 6000 characters across all embeds. Normal message text has a separate limit. Each V1 embed supports up to 25 fields.

All design sections are optional. Once you add a field, both its name and value are required. Remove unused fields. Side-by-side enables inline fields, whose final layout depends on Discord and screen width. An author link or icon requires an author name, a title link requires a title and a footer icon requires footer text. Optional links must be complete HTTP(S) addresses. The timestamp shows the sending time.

Role and channel pickers are available in normal message text, the V1 description and field values. These mention pickers are unavailable in author, title, footer and field names. Server emojis can be used in those text sections. Author URL and title link are URL-only inputs without roles, channels or emojis. Mentions in classic embeds do not notify anyone.

Link buttons

V2 groups up to five link buttons into one action row. V2 uses the overall component budget instead of the V1 limit of five rows.

Link buttons open websites and do not assign roles. Each added button requires a label of up to 80 characters and a complete HTTP(S) URL of up to 512 characters. An emoji is optional. Buttons can be reordered and removed. V1 displays them below the embeds with up to five buttons per action row and five rows overall, so at most 25 buttons. V2 displays them inside their container and counts them and their action rows towards the 40-component budget.

Create composition

The internal name is required even when saving only a draft. The editor allows up to 50 characters. New compositions receive a suggested name that you can edit. The name appears only in the dashboard. Publishing requires an accessible target channel and visible text, an embed or a complete link button. A description or image does not require a title. An empty draft does not yet need message content.

Required Discord rights

In V1, mentions in normal message text can notify users, but classic embeds cannot. In V2, text blocks can also trigger mentions. For @everyone, @here and roles that are not generally mentionable, Fjord needs the corresponding Discord permission. Review mentions before publishing.

View Channel and Send Messages are needed for every publication. Embed Links is needed for classic embeds and their images. Attach Files is required when sending local image files once. Saving a draft does not yet publish a Discord message.

1. Open Embeds in the dashboard.
2. Select New Composition and assign an internal name.
3. Add normal message content if necessary.
4. Design the first embedding and add additional embeddings if necessary.
5. Check the result in the Discord preview.
6. Choose a target channel for publishing or leave the channel blank to save only a draft.

Message content

Normal message content appears above the embeds and can contain up to 2,000 characters. Roles, channels and server emojis can be used via the selection in the editor.

In V1, mentions in normal message text can notify users, but classic embeds cannot. In V2, text blocks can also trigger mentions. For @everyone, @here and roles that are not generally mentionable, Fjord needs the corresponding Discord permission. Review mentions before publishing.

Design embeds

Discord only shows the author icon when an author name is also set. Enter a name above so the icon appears in the preview. Discord only shows the footer icon when footer text is also set. Enter text above so the icon appears in the preview.

V2

An image block can contain a gallery of up to ten images. Use “+ Another image” to add images, which can be removed individually. Each image and thumbnail has an optional description of up to 80 characters and an optional spoiler setting. A section supports up to three texts of up to 4000 characters each. Use “+ Another text” to add up to two additional texts. Accessory lets you choose between a thumbnail and a link button. The link button requires a label of up to 80 characters and a complete HTTP(S) URL of up to 512 characters. Emoji and disabling are optional. Additional section texts and the accessory button count towards the component limit. Individual images in a gallery do not count as additional components.

In V2, containers and images, including thumbnails, can be marked as spoilers. Their content is initially hidden and revealed by clicking.

V2 offers up to ten containers with separate accent colours. Use text blocks or sections with an optional thumbnail on the right, each supporting up to 4000 characters and Markdown. Separators can show a line or just spacing, with small or large spacing. Add, copy, remove and reorder blocks with the arrows. Empty text and image blocks produce no visible content. V2 text sections offer role, channel and server-emoji pickers.

V2 has no classic author fields, title-link inputs, inline fields, footer icons or timestamp switch. Add headings and links using Markdown in text blocks. Use the Markdown example below for a small footer and the time token for a timestamp. V1 does not offer freely arranged V2 blocks. Both formats cannot be mixed in one message.

-# ... · {time.full}

V2 has a shared limit of 40 components for the entire message. Containers, text displays, sections, thumbnails, image galleries, separators, action rows, buttons and select menus each count. Menu options do not count individually. Automatically added separators and controls also use the budget. For example, a container with text, an image, a separator and a button with its action row uses six components. Ten containers therefore cannot all be filled without limit.

Use images

Image limits apply per file. In V1, author icons, thumbnails and footer icons may each be up to 5 MB. The large-image limit matches the V2 image-block limit shown below. PNG, JPG/JPEG, WebP and GIF are supported. Choose a file to replace an image, or Remove to clear its slot. Author and footer icons are invisible without their corresponding text.

Choose PNG, JPG/JPEG, WebP or GIF. Images upload when saving. Thumbnails allow up to 5 MB, image blocks up to 10 MB. One-time sending in the embeds module allows up to ten local images totaling 20 MB.

Save and publish

If the managed message is already missing in Discord, saving again republishes it. A duplicated composition keeps its format but starts without a publication channel and is independent of the original.

Save as draft

Leave the channel selection blank and save. The draft remains available in the dashboard without creating a Discord message.

Publish permanently

Select a channel and save. The created Discord message remains linked to the composition. Subsequent changes will be updated in the same message when saved.

Postpone publication

If you choose a different channel for a composition that has already been published, the next time you save it, the new message will be created first and then the old one will be removed.

Remove publication

Remove Post only deletes the managed Discord message. The composition remains as a saved draft.

Delete composition

Deleting a composition removes its saved record and stored images. An already sent Discord message is not deleted and may lose image references. To remove the managed message too, explicitly remove its publication first. Messages sent once are not managed afterwards.

Manage and duplicate

Saved compositions can be opened, renamed, duplicated and deleted. Up to ten embeddings can be created, rearranged and duplicated within a composition. Duplication is prevented if doing so would exceed Discord's number or text limits.

You can switch between compositions and the overview within the module. Unsaved changes are retained. Save or discard all pending changes before leaving the module. The shared save bar also remains visible in the overview. Save applies all pending composition changes. Cancel discards them. This also includes changes in compositions that are not currently open.

Fix errors

Composition placeholders

Use the following placeholders in normal message content in either version and in classic V1 text fields. They are replaced when sending or updating, not continuously refreshed. These server, channel and bot placeholders are currently not replaced in V2 blocks. The time token described above works there. Member placeholders and dynamic avatar images belong to the welcome module.

Requirements and limitations

A valid design does not require every optional section. Colour alone or empty blocks do not supply visible content for publishing. The preview does not send a message or replace testing in the target channel. Neither editor offers polls, stickers, forms or freely programmable actions. Available data and editing also depend on your granted dashboard permissions.

Preview, spoilers and image files

In the V2 preview, a single gallery image keeps its aspect ratio. Multiple images form a grid with equally sized 16:9 crops. Two or four images use two columns, while three and five to ten images use three columns. A thumbnail appears to the right of the section text. The image description provides alternative text rather than an extra visible caption.

Image and container spoiler switches belong to the V2 editor. Individual gallery images and thumbnails can be hidden independently. A container spoiler hides its contents while keeping the outer frame visible. Clicking reveals the preview without changing the saved spoiler setting. Members can also reveal spoilers by clicking them in Discord.

Message images accept PNG, JPG/JPEG, WebP and GIF. The file type must match its image contents. Renaming an HTML or SVG file does not make it a supported image. The limits in the image tables still apply to each file. If a local image is rejected or can no longer be read, select the original file again and save once more.

Markdown text areas support web and email links. The preview opens HTTP(S) and mailto links, but does not open local file or Blob links. Author links, title links and link buttons require complete HTTP(S) URLs. The preview does not publish a message. Check the saved result in Discord, where the appearance can vary by client and screen width.