Backgrounds in presentations

Last reviewed on 28 April 2026.

Presentation backgrounds look like web backgrounds and behave nothing like them. A slide is read at a different distance, under different lighting, on a different display, and at a different reading speed than a web page. The same gradient that works as a hero on a marketing site can flatten into mush on a conference projector; the elegant near-black that reads as luxurious on a phone can look murky on a laptop screen at the back of a meeting room. This page covers the distinctions that matter, and the practical decisions a designer needs to make once they know about them.

Aspect ratios and the safe-area problem

Modern slide software defaults to 16:9 (Keynote, PowerPoint, Google Slides, Figma Slides). 4:3 still appears in academic and corporate settings where the projector hardware is older. A background designed for one aspect ratio rarely survives an automatic conversion to the other — content that sat comfortably in the centre of a 16:9 frame can end up cropped or pushed off-balance in 4:3, and vice versa.

The defensive practice is to design with a safe area in mind: keep the focal point of the background within roughly the centre 80% of the frame, and assume the outer 10% on each side may be cropped, masked by a logo bar, or hidden behind the presenter's body if you are projecting onto a stage. Headlines and key elements should sit even further inside that, in the centre 60%.

Projection versus screen reading

A laptop screen renders perhaps 300–500 nits of brightness in a dim conference room; a projector throws 2,000–5,000 lumens onto a screen that ambient light is also fighting to brighten. The result is dramatic contrast compression. Subtle gradients that read clearly on a designer's monitor become invisible on a stage; near-black canvases drift toward grey under projector bleed-through; saturated brand colours wash out into pastels.

Two practical adjustments make slides survive projection. First, increase the contrast of the background-to-foreground relationship beyond what looks correct on screen — a deck designed at 7:1 contrast will read at perhaps 4:1 once it hits a real projector in a real room. Second, avoid relying on subtle tonal differences within the background itself. A two-stop dark gradient from #0a0a0a to #1a1a1a has plenty of presence on a phone and almost none on a projection screen; widen the gradient or replace it with a flatter, higher-contrast canvas.

Light decks and dark decks

Light backgrounds are the safer default for presentations that will be projected, because projector light adds to ambient light rather than competing with it. A near-white slide stays bright and readable in a half-lit room. Dark decks have made a comeback in tech-industry presentations, and they can be magnificent on a fully-controlled stage with the room lights dimmed; in a conference room with sun coming through the windows, the same dark deck can be unreadable.

The practical compromise is to design two versions of any deck that travels: a "stage" version with deeper saturation and harder contrast, and a "room" version with lighter backgrounds and stronger type weights. Most slide tools support a master template that can be swapped in five minutes before the talk begins. The light backgrounds and black backgrounds hubs cover the underlying tonal trade-offs.

Type on slide backgrounds

Reading speed on slides is much faster than reading speed on a web page. The audience has perhaps three to seven seconds before the presenter advances; type on the slide has to be legible at a glance, not on careful reading. That puts the contrast bar higher than for body content on a website. WCAG AA's 4.5:1 minimum is a floor, not a target; aim for 7:1 or above for headline type on a slide, and treat anything subtler as a deliberate choice you have a reason for.

Type weight matters more on slides than on the web. Light and thin weights that read as elegant in body text on a website tend to disappear at projector distance; medium and bold weights survive. The accessibility guide covers contrast measurement; the practical addition for slides is to verify the deck on a low-brightness monitor as a proxy for projector behaviour.

Animation and motion

Animated slide backgrounds — looping gradients, drifting particles, video loops — are tempting and almost always a mistake in live presentation. They compete with the speaker for the audience's attention; they trigger motion sensitivity in audience members who would not see them on a static web page; and they can introduce frame-rate stutter when the presentation app is also running a remote-control connection or a video conference overlay.

If a deck must include motion, two rules avoid the worst outcomes: the motion should be confined to specific feature slides rather than running on every slide, and the motion should be slow enough that it never competes with the speaker's pacing — a full loop should take 20 seconds or longer, not 4. The animated gradient sub-page covers the underlying technique.

Templates, brand systems and consistency

The single most useful design decision for a deck that will be used by many people is to ship a template with a tightly constrained set of background options. Three to five master backgrounds — for example, a title slide, a section divider, a content slide, a quote slide and a stats slide — covers almost every real need, and prevents the slide-by-slide drift that turns a clean deck into a visual mess after the third hand-edited copy.

The constraint is also a kindness to non-designers who have to use the template. A template that offers infinite background flexibility produces inconsistent decks; a template that offers five options produces decks that look composed, even when the person using it has no design training.

Print, handout and PDF behaviour

Decks are routinely exported as PDF for distribution and as printed handouts. Light backgrounds with dark type print correctly; dark backgrounds with light type print as huge ink-saturated rectangles that can fail on shared office printers and read as harsh on the page. If the deck is likely to be printed, a separate light-canvas variant for the print version is worth maintaining; alternatively, a single canvas that uses a near-white default with darker accent slides will print readably without a second template.

Backgrounds are doing more work in a presentation than they do on a web page, because they have less time to do it. A deck whose backgrounds clear the bar above will almost always look more composed and read more clearly than one whose visual decisions were made for an audience sitting at a desk.