Brand a SharePoint form with your colours, logo, and fonts

The brand kit

Forms 365 Web has a brand kit. You set the brand once and forms pick it up, so they carry your look rather than a generic one. For a public form that a customer sees, that consistency is the difference between something that feels official and something that feels bolted on.

Imagery and layout

A media library holds the images you reuse, so a header image or a logo is a pick rather than a re-upload each time. Layout blocks like panels and headings let you group fields the way a real document reads, which does as much for how branded a form feels as the colours do.

Custom CSS when you need pixel control

For an internal SharePoint list form, Forms365 Workspace includes a code editor where you can add your own HTML and CSS. Most teams never open it, but when a brand guideline is exact about a colour or a font weight, the code editor is there to match it precisely. The designer handles the layout, and the styling that makes a Workspace form match your brand is set in that code editor.

Keep it consistent across forms

Branding is most useful when it is not redone by hand on every form. Setting it once and reusing it, through the brand kit on the web side and reusable form templates on the internal side, keeps a set of forms looking like they came from the same place. That matters more as the number of forms grows.

Why it matters more on a public form

The two products carry different stakes here. An internal list form is opened by staff who already know where they are, so branding is mostly about looking deliberate rather than default. A public form is often the first thing a customer, applicant, or contractor sees from you, and it usually arrives through a link with no surrounding website to vouch for it.

That context is what makes branding a completion-rate question rather than a decorative one. Somebody asked to enter bank details or upload an insurance certificate on a page that looks generic has a reasonable instinct to stop and check whether the request is genuine. Your logo and your own wording remove that hesitation.

Get these four right first

Most of the benefit comes from a short list. On Forms 365 Web you can do all of it without opening a code editor. On an internal list form the logo and the button wording are just as easy, while the colour and type parts go through the code editor.

• The logo, at a sensible size. Recognisable, not dominating the first screen. It is there to identify you, not to be the headline.
• One accent colour on the things people act on. The submit button above all. Colouring everything is the fastest way to make a form look worse.
• Keep the characterful face for headings. A form is a working document, so the fields themselves need to stay legible.
• Put your own words on the buttons. "Submit request" beats "Submit", it costs nothing, and it does more for how bespoke a form feels than any colour does.

Check it on a phone before you ship

Branding is where a form most often breaks on a small screen. A wide logo that sits neatly beside a heading on a desktop will wrap or shrink to nothing on a phone, and a colour pairing that reads comfortably on a large monitor can lose contrast on a dim handset outdoors. The designer has a preview with device toggles, so switch to the mobile view before publishing rather than after somebody tells you.