How to Record Xcode
Record Xcode with readable code and clean layouts. Guide for iOS tutorials, SwiftUI demos, simulator recordings, and code review walkthroughs.
When you’d need to record Xcode
iOS development tutorials
Record SwiftUI or UIKit tutorials showing code, preview, and simulator simultaneously. Xcode's integrated environment means the full dev cycle happens in one window — perfect for recording.
App demo recordings for App Store submissions
Record your app running in the iOS Simulator for App Store preview videos or TestFlight documentation. Screenify's iOS Simulator recording mode captures the simulator at native resolution.
Code review walkthroughs for iOS teams
Walk through a pull request in Xcode's Source Control navigator. Show the diff, explain changes file by file, run the build to demonstrate the changes work.
WWDC feature demos and migration guides
After WWDC, record tutorials showing new Xcode features, API changes, or Swift language updates. The iOS dev community consumes this content heavily in June-July every year.
Recommended settings
Things to know
- •Xcode is macOS-only and extremely resource-intensive — builds, indexing, and previews compete with screen recording for CPU/GPU
- •iOS Simulator launches as a separate window that needs its own capture or combined full-screen recording
- •Xcode's SwiftUI Preview canvas renders live and consumes significant GPU — may cause recording frame drops
- •Build output in the bottom panel scrolls rapidly during compilation — unreadable at recording speed
Step-by-step
- 1
In Screenify Studio, select Window Capture and pick the Xcode window.
If you'll show the iOS Simulator, either use Full Screen capture to get both, or record Xcode and Simulator separately.
- 2
Open Xcode and your project. Wait for indexing to complete — the progress bar in the top center shows 'Indexing...' during startup. Recording while Xcode is indexing causes UI lag and makes the editor unresponsive.
- 3
Set your editor layout before recording. Close panels you won't use: hide the Navigator panel (Cmd+0) or Inspector panel (Cmd+Option+0) if not needed. Show only what you'll reference.
- 4
Increase Xcode's editor font size: Xcode > Settings > Themes > select your theme > click the font size 'T' icon > set to 14-16pt. Default is 11pt — unreadable in recordings.
- 5
Start recording. When running the app (Cmd+R), Xcode's build output scrolls in the bottom panel. Mute the build output verbally ('building now, this takes a few seconds') and wait for the Simulator to launch before continuing your explanation.
For SwiftUI previews and debugging
- 6
For SwiftUI tutorials, arrange the editor and Canvas preview side by side. Resize the Canvas to show the preview at a usable size — default split often makes the preview tiny. Cmd+Option+Return toggles the Canvas.
- 7
To record the iOS Simulator separately: use Screenify's Custom Area capture and drag to exactly match the Simulator window frame. This gives you a clean phone-shaped recording without Xcode's UI.
- 8
When demonstrating debugging, open the Debug Navigator (Cmd+7) and the Debug Console (Cmd+Shift+Y). Set breakpoints before recording, then Cmd+R to run. Step through code with F6 (Step Over) while explaining each line.
Pro tips
Keyboard overlay is critical for Xcode. Cmd+R (Run), Cmd+B (Build), Cmd+Shift+O (Open Quickly), Cmd+. (Stop), Cmd+7 (Debug Navigator) — Xcode is a keyboard-driven IDE. Without overlay, viewers see your app magically building and running with no indication of what you pressed.
Auto-zoom on the Issue Navigator. When a build fails, Xcode's Issue Navigator (Cmd+5) lists errors and warnings in 11px text with file paths and line numbers. Auto-zoom catches your click on a specific error and zooms in so viewers can read 'Type Int is not convertible to String at line 42'.
Wait for indexing before recording. Xcode indexes your project on launch — autocomplete, jump-to-definition, and syntax highlighting don't work until indexing completes. Recording during indexing shows a broken-looking IDE with missing features.
Record simulator and code separately if needed. Showing both Xcode and iOS Simulator in one recording means both are small. For tutorials, record the code explanation in Xcode first, then record the simulator demo separately. Combine in the timeline editor.
Common mistakes
Recording while Xcode is still indexing. Autocomplete doesn't work, syntax colors are missing, and jump-to-definition fails. Viewers think your project is broken. Wait for the indexing progress bar to disappear before recording.
Leaving the default 11pt font size. Xcode's default editor font is 11pt SF Mono. After video compression, Swift code becomes an unreadable gray block. Go to Xcode > Settings > Themes > increase to 14-16pt.
Not accounting for build time. You press Cmd+R and wait 30 seconds for a clean build while nothing happens on screen. Either pre-build before recording (Cmd+B, wait for 'Build Succeeded'), or fill the dead air with explanation: 'while this builds, let me explain what this code does.'
Showing Xcode's 'Welcome to Xcode' screen. It lists your recent projects with full file paths: '/Users/brian/Clients/SecretApp/SecretApp.xcodeproj'. Open your project before starting the recording, or disable the welcome screen in Xcode > Settings > General.
Related apps
Related guides
Record Software Tutorials
Educators, YouTubers, course creators, and developer advocates who produce instructional content
Record Bug Reports
QA engineers, developers, product managers, and support agents who file or triage bugs
Record Code Reviews
Senior developers, tech leads, and engineering managers who review pull requests regularly
Record Training Course Content
Course creators, bootcamp instructors, corporate trainers, and educators building learning content on platforms like Udemy, Teachable, or internal LMS
Record Xcode with Screenify Studio
AI auto-zoom on clicks, instant captions in 50+ languages, cursor highlighting, and studio-grade export. Free plan, no watermark.
Try Screenify Free
