How to Freeze Tracks in Logic Pro and Save CPU
Freeze a heavy instrument or effect chain without committing it permanently, and choose the right freeze mode for the job.
A heavy synth or plug-in chain doesn't need to run live while you finish the rest of a Logic project. Freeze the settled track and Logic Pro renders a temporary audio file for playback. Click the snowflake again when you want the original instrument, regions and plug-ins back.
To freeze tracks in Logic Pro, use one short pass: show the Freeze button, choose Source Only or Pre Fader in the Track inspector, click the snowflake, then press Play. That last step matters. Clicking the button arms the track. Play triggers the render.
This guide was checked on August 26, 2026 against Apple's current Logic Pro for Mac 12.3 User Guide and the 12.3.1 release baseline. The version check catches one detail that old tutorials often get wrong: in current Logic, Source Only is green and Pre Fader is blue.
How to freeze a track in Logic Pro
- Show the Freeze control. Choose Track > Configure Track Header, or press Option-T. Enable Freeze in the Buttons section if the snowflake is not already visible.
- Select the track. Open the Inspector with I if it is hidden, then expand the Track section.
- Choose the mode. Set Freeze Mode to Source Only or Pre Fader. The next section explains which one fits the job.
- Click the snowflake. The Freeze button is in the track header, beside the other track controls.
- Press Play once. Logic Pro creates the freeze file before playback continues.
- Listen at the problem section. Confirm that the part, automation and effect tails behave as expected.
To unfreeze, click the active snowflake again. Make the edit, then repeat the same process. Apple's current Freeze instructions describe the same click, choose mode, Play, and unfreeze sequence.
If you want to freeze several tracks, click and hold one Freeze button, then drag up or down across the other track headers. Apple documents this swipe as a way to switch multiple Freeze buttons to the same state. Press Play after the tracks are armed so Logic can render them.
Source Only vs Pre Fader: choose by what must stay editable
The two modes do different work. “Pre Fader” doesn't mean “before all processing.” It means the rendered point sits before the channel fader, after the track's insert effects.
| Freeze mode | What Logic renders | What stays live | Use it when |
|---|---|---|---|
| Source Only Green in Logic 12.3 | The source signal, including a software instrument or processor-heavy Flex work | Track effect plug-ins | The instrument or Flex processing is expensive, but you still want to adjust EQ, compression or other inserts |
| Pre Fader Blue in Logic 12.3 | The source signal and track effect plug-ins | The channel fader stage and supported track controls | The instrument and insert chain are settled and you want the larger reduction in live processing |
Start with Source Only when the sound source is the problem but the mix is still moving. A sampled instrument, a dense synth patch or heavy Flex Time processing can be printed temporarily while the inserts remain available.
Choose Pre Fader when the full channel-strip sound is stable. Logic then includes the effect plug-ins in the freeze file. That's usually the better mode for a finished amp-sim chain, a CPU-heavy vocal stack or a virtual instrument whose sound design and inserts are no longer changing.
Do not identify the mode from an old screenshot. Apple's 10.7 documentation showed the colors the other way around. The current 12.3 page and current Track inspector are the reliable reference for this guide.
What Logic Pro does when it freezes a track
Logic Pro creates a temporary audio freeze file and plays that file instead of calculating the original track in real time. The original track isn't deleted. Its regions, instrument, plug-ins and settings return when you unfreeze it. Freeze is a CPU decision. If the real job is preventing accidental edits, compare Track Protect and Freeze before committing the track.
Apple says the freeze file includes the output of the processing chosen by the mode and track automation. While the track is frozen, track controls such as mute and solo remain available, but the track content cannot be edited. You can't move a region, change a MIDI note or mute one region until you unfreeze.
That restriction is useful when a part is genuinely settled. It's irritating when the arrangement is still changing every few minutes. Freeze the expensive tracks you're unlikely to touch for the next stage, not every track by habit.
Does freezing tracks really save CPU?
Yes, when the bottleneck is live processing. A software instrument and its insert chain no longer need to be calculated on every playback pass. The cost moves toward playing an audio file from storage.
That trade explains why Freeze isn't a universal system-overload cure. Open Logic's Performance Meter and watch the same section that fails:
- If Processing Threads peaks, freeze the heaviest settled instrument or effect chain and test again.
- If Drive I/O peaks, do not keep freezing software instruments blindly. Apple warns that the extra disk playback can make that bottleneck worse.
- If neither meter reproduces the problem, check the audio buffer, selected live instrument, plug-in behaviour and interface path before blaming track count.
The full decision tree belongs in our Logic Pro system overload guide. Freeze is one precise fix inside that process, not the process itself.
Freeze vs Bounce in Place
Both features render live processing to audio, but they solve different jobs.
| Choose | When you need | What happens next |
|---|---|---|
| Freeze | Temporary CPU relief with easy recall | Logic plays a hidden freeze file; unfreeze to restore the original track for editing |
| Bounce in Place | A new editable audio track or region inside the project | Logic creates visible 24-bit audio at the project sample rate, with choices for handling the source |
Apple's current Bounce in Place overview says Freeze is easier to return to the original state. It also notes that freeze files use 32-bit floating point, while Bounce in Place creates 24-bit audio at the project sample rate. Those formats are implementation details, not a reason to expect Freeze to sound “better.” Choose by workflow.
Use Freeze while the production still needs reversible headroom. Use Bounce in Place when audio itself is the next working format, perhaps for chopping, reversing, handoff inside the session or a deliberate commitment. Our Bounce in Place vs Export guide covers the render choices without mixing them into this tutorial.
A practical freeze workflow for a busy project
- Find the expensive track. Reproduce the overload and watch Processing Threads rather than guessing from the number of plug-ins.
- Save the project. Freeze is reversible, but a normal save gives you a clear recovery point before changing several tracks.
- Freeze one candidate. Start with the dense instrument or insert chain that is musically settled.
- Choose the least restrictive useful mode. Use Source Only if you still need live inserts. Use Pre Fader if the full chain is stable.
- Replay the exact failure point. Check both the sound and the Performance Meter.
- Stop when the project is stable. Leaving a few active tracks editable is often faster than freezing everything and repeatedly waiting for new renders.
This workflow keeps Freeze attached to evidence. It also avoids a common loop: freeze ten tracks, change the arrangement, unfreeze ten tracks, then render them all again.
Fix the common Freeze problems
The snowflake button is missing
Press Option-T or choose Track > Configure Track Header. Enable Freeze in the Buttons section. You can also Control-click a track header and open its Track Header Components menu. The current Track Header guide documents both routes.
I clicked Freeze, but nothing rendered
Press Play. The snowflake marks the track for freezing, and the next Play command creates the file. If you armed several tracks, Logic renders each one before ordinary playback continues.
I cannot edit the frozen track
That's expected. Click the snowflake again, edit the original regions or plug-ins, then refreeze. Freeze is a reversible playback state, not a new editable audio region.
Freeze is unavailable on this instrument
Check whether the track uses a multi-output software instrument. Apple's current documentation says Track Freeze is not available for multi-output software instruments. Do not flatten complex routing just to make the button work. Decide whether Bounce in Place, track export or turning off settled subtracks fits the session better.
The system overload still happens
Confirm which meter is peaking. More freeze files won't repair a Drive I/O bottleneck, and a single selected live software instrument can still dominate one processing thread. Return to the Logic Pro troubleshooting hub and follow the symptom rather than adding more changes at random.
The frozen version sounds different
Unfreeze and compare the same cycle range at the same level. Check whether the track depends on live input, external hardware, a sidechain, randomized modulation or routing outside the rendered point. Do not keep a questionable freeze just because the CPU meter improved. Use Bounce in Place or a real-time render when the routing needs a deliberate printed result.
Logic Pro Freeze FAQ
Does freezing tracks reduce CPU use in Logic Pro?
Yes, when live instruments or effect plug-ins are the bottleneck. Logic Pro plays a temporary audio freeze file instead of calculating the frozen processing in real time. That shifts work toward disk playback, so freezing can be the wrong fix when the Drive I/O meter is already peaking.
What is the difference between Source Only and Pre Fader freeze?
Source Only freezes the source signal without the track's effect plug-ins, which keeps those inserts available for changes. Pre Fader includes the effect plug-ins in the freeze file and usually removes more live processing. In the current Logic Pro 12.3 interface, Source Only is green and Pre Fader is blue.
How do I unfreeze a track in Logic Pro?
Click the active snowflake Freeze button in the track header. Logic Pro restores the original track and its plug-ins so you can edit it, then you can freeze it again after the change.
Why is the Freeze button missing in Logic Pro?
Press Option-T or choose Track > Configure Track Header, then enable Freeze in the Buttons section. If Freeze is still unavailable, check the track type: Apple states that track freeze is not available for multi-output software instruments.
Should I freeze or bounce in place in Logic Pro?
Freeze when you want temporary CPU relief and an easy return to the original instrument, plug-ins, and automation. Use Bounce in Place when you deliberately want a new editable audio track inside the project.
Can I edit a frozen track in Logic Pro?
You can use track controls such as mute and solo, but Logic Pro does not let you edit the track's regions or other track content while it is frozen. Unfreeze it, make the edit, and freeze it again.
Freeze the track that's expensive and settled, then leave the rest of the session easy to change. That small decision saves more time than treating every snowflake as a permanent commitment.
