Conference Presentation Design: How to Build a Talk That Reads From Row 30

You are giving a talk at a conference in six weeks. Twenty minutes on stage, a room of two hundred people, most on laptops, half already tuned out from three talks in a row. Someone is recording it for the conference YouTube. Someone else will screenshot your best slide and post it before you leave the stage.

The slides have to work in all three places: the room, the video, and the screenshot. That is a harder brief than most decks handle, and most conference decks visibly do not handle it. They are built to be talked over, not to work as a document on their own.

Here is how to design a conference deck that reads from row 30, holds up on a livestream, and gets shared.

How long should a conference presentation be?

Most conference slots are 15, 20 or 25 minutes of talk plus 5 to 10 minutes of Q&A. A safe rule for slide count: one content slide per minute of talk, plus a title and a closing. So 18 to 22 slides for a 20-minute talk. Faster if you have a lot of visuals, slower if any single slide carries a big idea.

Do not run long. Rooms get punishing when a talk overruns, and conference chairs will cut Q&A to catch up. A tight 18 minutes ending on a strong question beats a loose 22 minutes cut off by the moderator.

What has to be true of every conference slide

Four rules, in order of importance:

1. Readable from the back of the room. Body text at 24pt minimum, ideally 28. If your slide has body text at 18pt you are designing for the front three rows.
2. Legible in the livestream. Assume 720p compression on someone's phone. High contrast, no thin gray text on white, no red text on black. Aim for near-black on near-white or the reverse.
3. Complete on its own. Someone will screenshot a slide and post it out of context. It should still make sense with a caption of "loved this from @yourname's talk today".
4. One point per slide. If a slide has two points, split it. The audience only remembers what the slide focused on.

The livestream and screenshot rules are the ones most academic and technical decks miss. A slide with three axes, a legend and eight lines is fine in a paper. It is unreadable in a compressed livestream and worthless as a screenshot.

Structure of a strong 20-minute conference talk

Not all talks follow the same shape, but most good ones do:

1. Title slide. Title, your name, affiliation, conference and date. This is on screen while you are being introduced. Make it look like the poster for a real talk, not a Word document.
2. The hook. One slide that tells the audience why they should stay. A striking result, a paradox, a question. Not "here is my agenda."
3. The problem. Two to three slides establishing what is wrong or missing today. Concrete, specific, ideally with a visual anchor the audience remembers.
4. The insight. One slide with the new idea or finding, stated cleanly. This is the slide that gets screenshotted if the talk is good.
5. How it works. Three to six slides walking through the approach, method, or argument. Diagrams beat prose. One diagram slide is worth three text slides.
6. The evidence. Two to four slides of results. If you have one killer chart, spend a full slide on it, not a shared slide with a table.
7. What this means. One or two slides connecting the finding back to the problem. What now becomes possible or obvious that was not before.
8. Where to go next. A closing slide with your contact, the paper or write-up link, and one big question or invitation. Give them somewhere to click after the talk.

The hook is optional and skippable if your topic is famous enough. Everything else is standard.

Design rules that separate a strong deck from a homemade one

Almost every "professional-looking" conference talk is doing the same handful of things.

One font family, everywhere. Pick a clean sans (Inter, Söhne, Helvetica Now, or PowerPoint's built-in Aptos). Use it for titles, body text and chart labels. Two fonts is one too many for a conference talk.

Two colors, plus black and white. A primary accent (usually your affiliation's brand) and a secondary for contrast. Every chart uses those two colors. Every headline uses one of them. You will be surprised how disciplined this looks.

The same layout on every slide. Title in the same place, page number in the same place, content area in the same place. If a slide breaks the pattern (a full-bleed image, a data slide) the break is intentional and rare.

Big visuals. A chart takes 60 to 70% of the slide. A diagram takes at least half. If your visual is smaller than the whitespace around it, the visual is not the point of the slide and the slide should be about something else.

Findings in the slide title. "Retrieval-augmented models fail on rare entities" is a slide title. "Analysis" is a placeholder. A skimmer reading only your titles should follow your argument.

Charts, tables and code

Conference audiences are hard on visuals because they know them well.

Charts. Label axes with words, not variable names. Include the units. Use color for one dimension of contrast, not four. If a chart has more than five lines, break it into two charts or highlight one line and gray out the rest.

Tables. Rare, and small. Six rows and three columns maximum. If you have a bigger table, put it in a paper appendix and show a summary chart instead.

Code. If you have to show code, show 10 to 15 lines maximum, in a monospace font at a size the back row can read. Highlight the two lines that actually matter and gray out the rest. Copy-paste from a real IDE looks worse than an intentional slide.

Equations. Own slide, big, numbered if referenced. LaTeX-rendered as an image beats PowerPoint's equation editor for anything more complex than a simple ratio.

Handling the video and the screenshot

The two ways your talk survives outside the room are the recording and the screenshot. Both benefit from the same design decisions, plus one extra.

Give the screenshot slide a title that stands alone. The two or three slides that carry your main results should have titles that make sense pasted onto X or LinkedIn without any of the surrounding talk. "Retrieval-augmented models fail on rare entities" works. "Findings, part 1" does not.

Assume compression. Test the deck by shrinking it to 720p and looking at it on your phone. If you cannot read the axis labels, the livestream cannot either.

Include your handle. A small username in the footer of every slide means every screenshot cites you. This is a real distribution advantage; most talks skip it.

The rebuild path

Most conference decks are a slow assembly of the same slides you have used before, with a new results section pasted in. They look like it. The design is 2019 with a 2026 result on top.

Two paths get to a real-looking conference deck.

Rebuild by hand. Pick one font, two colors, one layout. Apply them across every slide. Redraw the charts with consistent axes and colors. Rewrite every slide title to state the finding, not the topic. This takes a full day, more if the results are new.

Rebuild with an AI deck tool. Upload your draft to PitchBoost. Point it at your lab, company or affiliation site for brand and colors. It rebuilds every slide on a consistent layout with real text boxes, real fonts and readable chart formatting, and returns an editable .pptx you can open in PowerPoint or Keynote to make final adjustments. The free redesign preview shows two of your slides in the treated version before you commit.

Every number on your slides carries over exactly, and the fact check removes any figure it cannot trace back to your deck, so a rebuild never quietly changes your finding.

What to send after the talk

The tail of a conference talk is more valuable than the talk itself. People who saw it once want to reference it. People who missed it want to catch up. Two things worth doing:

1. Send a shareable link, not a .pptx file. A link opens in a browser, shows up on phones, and tells you when it is opened. PitchBoost's viewer analytics reports how many people opened the deck after the talk and, on Pro, which slides they spent time on. That is real feedback on which parts of the talk landed.
2. Include the paper or write-up link on the closing slide. People screenshot the closing slide to find the paper later. Make sure the URL is on it, spelled correctly, in a font the back row can read.

The short version

A conference deck has to work in three places: the room, the livestream and the screenshot. That means big fonts, high contrast, one font family, two colors, one layout, one point per slide, and findings in the slide titles. 18 to 22 slides for a 20-minute talk. A killer visual on the insight slide and the evidence slides. Your handle in the footer. Your paper link on the closing slide.

If your current draft is a patchwork of old slides with new results pasted in, either spend a day rebuilding it by hand or use PitchBoost to apply one design across every slide and return an editable .pptx. The preview is free.

Talking at a conference soon? Upload your draft and see the redesigned version on two slides before you commit to a full rebuild.