Online Course Slide Optimisation: Faster Load, Sharper Text

The single biggest complaint in Teachable, Thinkific, and Kajabi support tickets is not video quality. It is slow quiz pages and blurry screenshots of code samples. Both problems live in the same place: the JPG export step between Keynote or PowerPoint and the course platform. This guide walks through the slide-to-JPG settings that cut bandwidth, sharpen code listings, and keep tiny on-slide footnotes legible on a 6-inch phone screen.

Imagine the typical student: they buy your course on a Tuesday evening, open the first lesson on their phone during the commute home Wednesday morning, and hit a quiz where the question image takes 11 seconds to load on flaky cellular data. Half of them tap away and never come back to that lesson. The video is fine. The slide JPG is what broke the experience. Fixing it takes a 20-minute export-settings audit and pays off across every student forever.

Background: why slide JPGs matter more than slide videos

Most online courses are 60 to 80 percent video, but the JPGs do the heavy lifting for the parts that are not. Quiz question images, downloadable cheat sheets, lesson thumbnails, "review what we covered" recap pages, and the cover images in the catalog all ship as JPGs. A bloated 1.8 MB JPG on every quiz question multiplied across a 60-lesson course adds up to gigabytes of student bandwidth — particularly painful for international learners on metered mobile data.

Course platforms also re-process JPGs aggressively. Whatever you upload gets re-encoded, resized to platform-specific bins, and served from a CDN. That second encoding pass amplifies any artifacts already in your source. A clean, well-compressed source produces a clean served image; a bloated quality-100 source produces a blocky platform-compressed delivery.

Step-by-step slide export workflow

1. Set slide size to 1,920 x 1,080. 16:9 HD is the right canvas for both retina display and platform delivery.
2. Use display-quality fonts. Inter, Roboto, or system sans-serif at 24 pt minimum for body text.
3. Export the deck to image batch. Keynote: File > Export To > Images > JPG High. PowerPoint: File > Export > Change File Type > JPG.
4. Inspect a sample slide. Open one exported JPG in your viewer and confirm dimensions match expectation.
5. Compress the batch. Run the entire folder through the JPG compressor at quality 82 to 85.
6. Generate WebP if self-hosting. Use the JPG to WebP converter for a 28 percent file size reduction with no visible loss.
7. Upload to the platform. Test on a mobile device with cellular data turned on.
8. Spot-check load time. Cold cache, mobile network, real student device. If a quiz takes more than 3 seconds, recompress harder.

Export settings per slide tool

Keynote and PowerPoint both export slides to image formats natively, but the defaults are wrong for the web. Keynote exports JPGs at quality 80 by default; that is fine for general use but smears code. PowerPoint defaults to 96 DPI; that is fine for projection but blurry at retina display sizes. Specifics:

• PowerPoint: File, Export, Change File Type, JPG. Set the size manually to 1,920 x 1,080 if your slides are 16:9. PowerPoint will ask whether to export every slide or just the current one — pick every slide.
• Keynote: File, Export To, Images. Format JPG, quality High. The exported folder names files Slide-001.jpg, Slide-002.jpg by default, which is exactly what you want.
• Google Slides: File, Download, JPEG image only exports the current slide. For batch export, save as PDF and then push through a PDF-to-JPG converter.

If you authored in Keynote and need to share the batch with a PC-only contractor, a Keynote to JPG conversion path handles the .key file directly. For PowerPoint files coming from a co-instructor, a PPTX to JPG converter runs the same conversion in your browser without needing PowerPoint installed.

The retina trick for crisp code samples

Screenshots of code in any modern course need to be exported at 2x the display size, because most students view on retina-density screens. If your code panel will display at 800 px wide on the course site, export the slide at 1,600 px wide. The browser scales it down and the text stays sharp. Skip this step and the syntax highlighting blurs into rainbow soup at the third line.

For maximum clarity on code-heavy slides, raise the font to 24 pt minimum and use a monospace font with strong character separation — JetBrains Mono, Fira Code, IBM Plex Mono, or Cascadia Code all render cleanly when exported.

Common mistakes and fixes

• Mistake: exporting at 96 DPI for the web. Fix: target pixel dimensions (1,920 x 1,080 or 2x display size) rather than DPI for screen delivery.
• Mistake: quality 100 source JPGs uploaded to a platform. Fix: 82 to 85 is the sweet spot. Platforms re-encode anyway.
• Mistake: 12 pt body type on slides. Fix: 24 pt minimum. Phone-screen students cannot read smaller.
• Mistake: PNG screenshots of code at low resolution. Fix: capture at 2x retina, convert via the PNG to JPG converter, then compress.
• Mistake: inconsistent quiz image dimensions. Fix: pick one aspect ratio (1,200 x 675) and stick with it across the whole course.
• Mistake: ignoring thumbnails. Fix: lesson thumbnails are the most-served asset; optimize them first.

Real-world examples

A six-figure Teachable instructor running a Python data science course saw mobile completion rates jump from 47 percent to 61 percent after a single audit that recompressed every quiz image from 1.8 MB average to 180 KB average. The video stayed identical; only the JPGs changed.

A Thinkific cohort coach for design fundamentals uses a strict 1,600 x 900 export at quality 85 across the entire course catalog. The result: a 38-lesson course bundles into 110 MB of total slide-image data instead of the 380 MB she started with.

A Kajabi creator running a workout course uses a single template with a fixed branded color palette pulled with the color palette tool. Every quiz image, every cheat sheet, every recap slide ships with the same visual identity, which raises perceived production value without taking longer to make.

Slide-platform comparison

Platform	Recommended slide size	JPG quality	Re-compresses uploads	WebP support
Teachable	1920 x 1080	82	Yes	Output only
Thinkific	1920 x 1080	82	Yes	Output only
Kajabi	1920 x 1080	85	Light	Output only
Udemy	2048 x 1152	85	Yes, multiple bins	No upload
Self-hosted WP	1920 x 1080	85	No (you control)	Yes

Compression: where Teachable and Kajabi diverge

Teachable applies a single re-compression pass to uploaded images and serves them through a CDN. Thinkific does the same. Kajabi compresses lightly but caches aggressively. Udemy re-encodes everything to its own internal sizes. The takeaway: feeding any of these platforms a quality-95 source is wasted, because they will re-encode anyway. Feed them quality 82 to 85. The difference between 95 and 85 on a slide JPG is invisible at student viewing distance, and the file size drops 50 to 65 percent.

Run your full slide export through the JPG compressor after Keynote or PowerPoint spits out the folder. A 60-slide deck that came out at 95 MB compresses to 28 to 35 MB with no visible quality difference on quiz pages.

WebP for self-hosted course portals

If you run your course on a custom WordPress or Next.js stack rather than a managed platform, serve slides as WebP. The format averages 28 percent smaller than equivalent-quality JPG, and every browser released since 2020 supports it. Generate the WebP set alongside the JPG using the JPG to WebP converter and use a picture element with both formats so older clients get the JPG fallback. Most managed course platforms do not let you upload WebP, so this is a self-hosted-only trick.

Quiz image conventions that boost completion

Quiz images convert better when they follow a consistent visual format. Same aspect ratio, same color palette, same font, same logo placement. Students answer faster because they are not re-orienting on every question. The most common format is 1,200 x 675 (16:9 cropped) at JPG quality 82, around 60 to 110 KB per image. That is small enough for instant load on 4G and clear enough for diagrams and code snippets.

Thumbnail strategy across the course catalog

Lesson thumbnails are the single most-served image asset in any course platform. Every catalog page, every dashboard, every progress widget pulls the thumbnail. A poorly compressed 600 KB thumbnail multiplied across 80 lessons turns the dashboard into a slug. Target 50 to 90 KB per thumbnail at 600 x 338 dimensions, quality 80.

Advanced tips that compound across a course

• Build a downloadable cheat sheet PDF for every module. Bundle 8-12 slide JPGs with the JPG to PDF converter. Students get a printable reference; you get a deliverable that justifies premium pricing.
• Use the aspect ratio calculator to plan cover images. Course platforms display catalog cards at 16:9 or 4:3; mis-sized covers crop awkwardly.
• Lock the brand palette. Run brand colors through the color palette tool and stick to five values across every slide.
• Generate AVIF for the catalog page. If your platform supports modern formats, the JPG to AVIF converter shaves another 25 percent off thumbnail size.
• Audit existing courses for slow lessons. The student-side analytics in most platforms show per-lesson load times. Anything over 4 seconds gets the recompress treatment.
• Serve responsive sizes for self-hosted. A 1,920 desktop, 1,080 tablet, 540 mobile srcset cuts mobile data by 70 percent.
• Strip EXIF. A slide JPG with embedded camera metadata is 4 to 18 KB heavier than necessary; multiply across 600 slides and it matters.

FAQ

Should I export each slide as JPG or as a single PDF?

Individual JPGs for in-lesson images; a bundled PDF (via the JPG to PDF converter) for downloadable cheat sheets. Use both.

My platform downscales everything anyway. Why bother optimizing?

Because the platform's re-encoding works from your source. A clean source produces a clean re-encoded delivery; a bloated source produces blocky artifacts after the platform pass.

Can I use HEIC for slides instead of JPG?

No platform accepts HEIC for slide uploads. Convert HEIC source photos via the HEIC to JPG converter before embedding.

What about animated GIFs for tutorial steps?

Animated GIFs work but are typically heavier than short MP4 clips. If you must use GIF, the GIF to JPG converter handles the case where you only need a single keyframe.

How do I batch-rename exported slides for upload?

Keynote and PowerPoint both export with sequential names. Use OS-level batch rename to prepend the module number: m03_slide_007.jpg.

Is dark mode versus light mode slide design a thing?

Yes. Dark-mode slides compress slightly better in JPG (fewer high-luminance pixels means less DCT work) and are easier on student eyes for evening study. Pick one mode and commit.

Should I version slide exports?

Yes — keep v1, v2 in the folder name. Replacing a slide later means re-uploading and clearing the platform's CDN cache.

Final pre-upload checklist

1. Slide deck exported at 1,920 x 1,080 minimum, quality 90 from the source app
2. Compression pass run to take quality down to 82-85 for upload
3. Code-sample slides exported at 2x display size
4. Quiz images cropped to a consistent aspect ratio across the course
5. Thumbnails optimized to under 100 KB each

The cheat-sheet PDF as a marketing asset

Beyond the in-course experience, the downloadable cheat-sheet PDF doubles as a marketing asset. Students who download the cheat sheet share it with peers; the PDF becomes a top-of-funnel discovery tool. Design the cheat sheet to stand alone — your name, course link, and brand visible — and bundle 8-12 slide JPGs using the JPG to PDF converter.

The pipeline is the same as the in-course slide pipeline but with extra attention to the cover page (course title, instructor, what the student will get) and the back page (clear call-to-action with the course enrollment link). Compress aggressively — 200 to 400 KB total for a 12-page cheat sheet is reasonable.

Email-gate the cheat sheet for new visitors. The trade is fair: free knowledge for an email subscription, and the cheat sheet itself demonstrates the production quality of the full course.

Edge cases: live cohort versus self-paced delivery

Live cohort courses (Maven, Wes Kao Bootcamps, the live tier of most platforms) treat slides differently from self-paced courses. Live slides display via Zoom or Riverside at presenter resolution (typically 1,920 x 1,080), and student attention is on the speaker, not the slide quality. Self-paced courses live and die by slide quality because the slide IS the lesson during quiz and recap moments.

For live cohorts, optimize for legible-at-glance design: large type, minimal text per slide, high-contrast colors. For self-paced, optimize for re-readability: more detail, code samples that survive zoom, well-labeled diagrams. The same source deck can produce both versions by adjusting font sizes and detail density.

Cohort replays land somewhere in between. A live session recorded for replay gets the live design but is consumed at self-paced cadence. Test the replay on a phone and adjust if any slide is unreadable.

Going deeper: mobile-first course design

By 2026, mobile accounts for 55 to 70 percent of online course consumption depending on the niche. Coding courses skew desktop; cooking and lifestyle courses skew mobile. Either way, slide JPGs that look fine on a 27-inch monitor often fail on a 6-inch phone: text too small, code samples unreadable, diagrams compressed below recognizability. The fix is to design for the smallest target first and verify on a phone before publishing.

The simplest test: take any new slide, screenshot the published lesson on your own phone, and try to read every word from arm's length. If you cannot, neither can your students. Bump body text, simplify diagrams, and split dense slides into two.

Slide deliverables beyond the platform

Most successful courses ship deliverables outside the platform too: a downloadable PDF workbook, weekly email summaries with embedded slide snippets, and shareable social-media graphics that drive new enrollments. Each format has its own optimization profile.

The workbook PDF bundles 30 to 60 slide JPGs through the JPG to PDF converter. The email summary embeds one or two key slides at 600 px wide — small enough to display inline, sharp enough to read. The social-media graphics crop the highest-impact slide to platform-specific aspect ratios (referenced via the social media image sizes guide) and live as a separate set in the marketing folder.

Versioning slides over course iterations

Courses evolve. Version 1.0 ships in January, version 1.1 in March with three updated slides, version 2.0 in August with a structural overhaul. Versioning the slide assets matters because students may have downloaded the old workbook and the platform may have cached the old quiz images. A clear file structure with course-name/v2.0/module-03/slide_07.jpg lets you update precisely without breaking older students' downloads.

When you push a v2.0, clear the platform's CDN cache (most platforms have a force-refresh in admin settings), notify enrolled students that the materials were updated, and offer the v1.0 workbook PDF as a legacy download for students who already engaged with the older content.

Pick the lesson that loads slowest in your current course and re-export its slides through the JPG compressor. Upload, clear the platform cache, and time the load on a mobile network. A 2 to 4 second improvement is normal. The image converter covers cover-image format swaps, the image info tool verifies the embedded profile and dimensions, and the tool index handles the cheat-sheet PDF and student-handout exports that fill out the rest of the course bundle.