Skip to content

Colours, fonts and logos

Read this page when a theme value you set seems to have no effect, or a logo or image shows in one place but not another.

The Brand, Text and Background controls in the builder are colour pickers, so anything you pick there works.

Colours can also arrive another way: in a blueprint you import. A blueprint’s theme can contain colours written as text, in any of these formats:

FormatExamples
Hex#1B76D1, #fff, #ffffff80 (eight digits add transparency)
Colour namewhite, rebeccapurple, transparent
rgb, rgba, hslrgb(27, 118, 209), rgba(0, 0, 0, 0.5), hsl(210 100% 50%)
Newer formatsoklch(0.7 0.15 250), oklab(...), lab(...), lch(...), hwb(...), color(display-p3 1 0 0)

color-mix() does not work. A colour in any other format is ignored and the form uses the default colour instead. So if a colour seems to do nothing, check it against this table first.

Both are picked from a list, in the builder and in the Admin Dashboard’s Default theme panel:

  • Rounded corners: Square, Subtle, Rounded, Very rounded, Pill.
  • Space between fields: Compact, Comfortable, Roomy.

Both lists also have Theme default and Custom. Custom takes a size such as 1rem, 12px, 0.5em or 0.

  • A negative size is refused when you save.
  • Anything that is not a size is ignored, like an unreadable colour.
  • A size from an imported blueprint that does not match a named option shows under Custom, unchanged.

Pick Font Family from the list, or leave it Not set:

  • Device fonts: Sans serif, Serif and Monospace, which every browser already has.
  • Web fonts (from 1.3): Inter, Roboto, Open Sans, Montserrat, Poppins, Nunito and Gelasio. Sliick Forms supplies these, so they show on Sliick Edge and on Experience Cloud pages with nothing to install or approve. The builder preview and the Default theme sample show them too.
  • Custom… lets you type your own list of font names.

A web font shows for forms in Latin-alphabet languages and in Russian. Gelasio and Poppins have no Russian letters, so a Russian form uses the device’s font instead. Japanese, Korean, Thai and Chinese forms always use the device’s font.

A font typed into Custom… is never downloaded, even if it has the same name as a web font: it shows only if it is installed on the respondent’s device, and otherwise the form quietly falls back to the default font. To use one of the seven web fonts, choose it under Web fonts.

Each form has its own logo, set in Logo URL on the builder’s Design tab. It must be an https:// address. Anything else, such as an http:// address or a file path, is ignored.

Image blocks follow the same rules as the logo about where a picture loads, so the rest of this section applies to them too. Give an Image block an https:// address as well: on Sliick Edge, anything else is ignored and the block shows nothing.

Where the form appears decides what a picture stored on another website needs before it shows. This is the most common reason a logo appears in one place but not another:

Where the form appearsWhat a logo or image on another website needs
The builder preview, inside SalesforceApprove the website in Setup, Trusted URLs (formerly CSP Trusted Sites), with images (img-src) allowed
The public form on an Experience Cloud siteApprove the website in Setup, Trusted URLs, with images (img-src) allowed for Experience Builder sites. Check that site’s own security settings too
A form on Sliick Edge (yourname.sliick.net, or embedded from it on your own site)Nothing to approve. Any https:// address loads, as long as the website lets anyone view the image. See On Sliick Edge, the picture must be public

The two places inside Salesforce are checked separately, so a logo can show on the live form and be blank in the builder, or the other way round. A Trusted URLs entry has a CSP context that says where it applies: All covers both places, while an entry for only Lightning Experience pages or only Experience Builder sites covers just one. You have to approve these yourself: Sliick Forms cannot approve an address you type in later.

If a logo will not load, the builder shows a short note instead of a blank space. It lists the likely causes: a wrong address, a website that cannot be reached, or a website not yet approved in Trusted URLs as the table shows. The builder cannot tell which one it is, so check the address first.

The builder showing a note in place of a logo that could not load

Tip: inside Salesforce, store the logo in your own org. For the builder preview and an Experience Cloud site, using a static resource, or a file on the Experience Cloud site itself, avoids the approval step. It is also more reliable: another website can move the image, slow it down, or stop serving it. On Sliick Edge, the address must open without signing in to Salesforce, so a static resource on your org’s own domain does not work there: see Using a file stored in Salesforce.

On Sliick Edge, the picture must be public

Section titled “On Sliick Edge, the picture must be public”

A logo or image on Sliick Edge still will not show if the website that holds it:

  • asks visitors to sign in before they can see it,
  • blocks its images from being shown on other websites (sometimes called hotlink protection), or
  • tells browsers to show the image only on its own website. A web developer would recognise this as the Cross-Origin-Resource-Policy: same-origin or same-site setting.

A quick check for the first one: open the picture’s address in a private browser window. If you are asked to sign in, or you get a web page instead of the picture, it will not show on Sliick Edge. If the picture opens, or the file simply downloads, no sign-in is needed. This check cannot spot the other two causes, so if the picture still does not show, ask whoever runs that website.

On Sliick Edge, an address that needs a Salesforce sign-in, such as a static resource on your org’s own domain, never shows. To use a picture stored in Salesforce, use the download address of a public link to the file. The address of a picture on any public website also works, as long as it meets the conditions above.

A public link opens a page, not the picture. When you create a public link for a file in Salesforce, the link you copy opens a page for viewing the file. Its address contains /sfc/p/. That page is a web page, not the picture itself, so it never shows as a logo or image.

The download address is the one to use. It contains /sfc/dist/version/download/. An admin can look it up in the Developer Console:

  1. Open the file’s details page in Salesforce (not just its preview), and copy its Id from the browser’s address bar. A file’s Id starts with 069.

  2. In the Developer Console, open the Query Editor and run this, with your file’s Id in place of the example:

    SELECT Name, DistributionPublicUrl, ContentDownloadUrl FROM ContentDistribution WHERE ContentDocumentId = '069000000000000AAA'
  3. Each row is one public link to that file. If there is more than one, pick the row whose DistributionPublicUrl is the link you created. If there are none, check that you copied the whole Id, and that the file has a public link.

  4. Copy that row’s ContentDownloadUrl into Logo URL, or into an Image block’s Image URL (https).

Opening the download address in a browser downloads the file rather than showing it. That is normal: it still shows as a picture on your form.

Caution: if you give the public link an expiry date or a password, the picture is likely to stop showing once the link expires, or not show at all. Leave both off for a logo or image.