June 18, 2025 Jun Do

How to Fix Zoom Stops in Blender

Executive SummaryBlender zoom stops at a glance
Blender 4.x and 5.x

Blender zooms toward a pivot point, and each step covers a fraction of the remaining distance. When the pivot sits in front of what you want to see, zooming slows to a crawl and seems to stop.

  • Fast fix: select the object and press Numpad . (View › Frame Selected), or Home to frame everything
  • Move past the pivot: Dolly View (Shift+Ctrl+middle mouse) or Walk Navigation (Shift+`)
  • Lasting fix: Preferences › Navigation: turn on Auto Depth and Zoom to Mouse Position
  • Model cut off up close: lower Clip Start in Sidebar › View

You scroll to zoom in on a detail and the view barely moves, or it stops short of the model however much you scroll. Nothing is broken: Blender’s viewport zooms toward a pivot point, and when that point is in the wrong place you can never reach the part you are looking at.

This guide explains why it happens, the quick fixes, and two preference settings that stop it happening again.

Checked against the Blender Manual (4.4–5.0), November 2026.

1. Why zooming stops

In perspective view, scrolling moves the view toward the point it orbits around, often called the pivot. Each step moves a share of the remaining distance, so steps get smaller as you approach the pivot and you never pass it. If the pivot was left behind somewhere, for example where an object you deleted used to be, or far in front of a small detail, the view slows down at the pivot and the model stays out of reach.

iRender
Why zooming in Blender seems to stop
Schematic
Top view: every zoom step moves the view a fixed fraction of the way to the pivotZoom stops: the pivot is in front of the objectobjectpivotviewafter 10 steps the view is almost at the pivot and every step gets shorter; the object never comes closerAfter Frame Selected (Numpad .): the pivot moves to the objectobjectpivotviewthe same steps now head into the object, so you can zoom in on itEach dot is the view after one scroll step; positions computed with a constant factor of 0.7 per step to show the shapePivot and zoom behaviour: Blender Manual, 3D Viewport Navigation; the step factor is illustrative
View position per zoom stepPivot (orbit and zoom center)Object
Computed example, factor illustrative

How to read the figure. Both rows are seen from above. Each blue or green dot is where the view ends up after one scroll step. In the top row the pivot (red crosshair) sits in front of the object, so the steps bunch up at the pivot and the object never gets closer; that is a zoom stop. In the bottom row Frame Selected has moved the pivot onto the object, and the same steps now lead into it. The step size is illustrative; the shape of the curve is the point.

2. Fix zoom stops, step by step

  1. Frame Selected. Select the object, or a vertex or face in Edit Mode, and press Numpad . (View › Frame Selected). The pivot moves to the selection and zooming works again. If you cannot see anything to click, select it in the Outliner.
  2. Frame All. Press Home (View › Frame All) to fit the whole scene in the view and reset the pivot to it.
  3. Dolly View. Press Shift+Ctrl+middle mouse and drag (View › Navigation › Dolly View). Dolly moves the view and the pivot forward together, so you can go past the old stopping point.
  4. Walk Navigation. Press Shift+` (View › Navigation › Walk Navigation) and move with W, A, S, D, Q and E like in a game. Click or press Enter to keep the new view, Esc or right-click to cancel. Fly Navigation is the alternative without gravity.
  5. Auto Depth. In Edit › Preferences › Navigation › Orbit & Pan, turn on Auto Depth. The pivot depth then follows what is under the mouse.
  6. Zoom to Mouse Position. In the same Preferences tab under Zoom, turn it on so zooming heads to the mouse cursor.
  7. Clip Start and End. If the model gets cut off as you get close, press N and in View lower Clip Start (default 0.01 m). Keep the gap between Clip Start and Clip End only as large as the scene needs; a very small Clip Start with a huge Clip End causes flickering surfaces.

In orthographic view (toggle with Numpad 5), zoom changes the scale of the view rather than moving it, so zoom stops are a perspective-view problem.

iRender
Getting unstuck: the commands and settings in order
Schematic
3D Viewport › ViewFrame SelectedNumpad .1Frame AllHome2View › NavigationDolly ViewShift Ctrl MMB3Walk NavigationShift `4Numpad 5 toggles Perspective / OrthographicOrtho zoom changes the view scale, not distanceEdit › Preferences › NavigationOrbit & PanAuto Depth5Orbit Around SelectionZoomZoom to Mouse Position6With 5 and 6 on, zoom heads to whateveris under the mouse cursor instead ofstopping at an old pivotSidebar (N) › ViewFocal Length50 mmClip Start0.01 mClip End1000 m7Objects cut off when you getclose? Lower Clip Start a little;keep the Start-to-End rangeas small as the scene allowsFast fix: select the object, press Numpad . (badge 1). Lasting fix: turn on badges 5 and 6 once in PreferencesOrange outline = the command or setting; badge = step number in the textLayout reconstructed from the Blender Manual (Navigation, Walk/Fly, Preferences Navigation, Sidebar View); default values shown; simplified
Command or settingOption on
Simplified mockup

How to read the figure. Start on the left: badge 1, Frame Selected, fixes almost every zoom stop, and badge 2 resets the whole view. Badges 3 and 4 move you through the scene when you need to go past the pivot. The middle panel holds the settings to change once: with badges 5 and 6 on, zooming follows the mouse and the problem rarely comes back. Badge 7 on the right is for a different symptom, the model being cut off up close, not for zoom stops.

Viewport navigation checklist

Use it when the view gets stuck.

ChecklistViewport navigation checklist
0 / 6 done
Tip: tick each item as you set up the job; the ticks reset when the page reloads.

SaaS or IaaS render farm: does navigation matter?

Viewport navigation never affects a render: frames come from the camera, not from your view. Navigation preferences such as Auto Depth live in your Blender preferences on the computer, not in the .blend. That only matters when you work on a remote machine.

CompareNeutral guide

Viewport work and render farms

How the two farm models fit depending on whether you need the viewport.

Your situationSaaS render farmIaaS render farm (iRender)
The camera and scene are final; you only need framesA good fit: upload and the farm renders the rangeWorks as well: open the file and render
You still need to look around and adjust the scene on a powerful machineThere is no viewport: the farm renders what you uploadYou work in Blender over remote desktop, with your own navigation preferences
Heavy scenes make your own viewport slowNot addressed: the farm only rendersA multi-GPU server keeps Cycles previews responsive while you set up shots
Rule of thumb: if the scene is ready, a SaaS farm is the shorter path; if you still need to work in the viewport on a heavy scene, rent the whole machine.

Working on a heavy scene on an iRender server

iRender
Works 1:1 like your own PC: we keep your setup, you just get more GPUs
IaaS render farm
Your workstationscene.c4d · .blend · .hip1 GPUYour iRender serverscene.c4d · .blend · .hipup to 8 GPUs=same setupWindows or Ubuntu desktopYour software, in the version you chooseYour plugins and scriptsYour licensesYour scene and render settings, unchanged1 GPUGPU power: the only difference1, 2, 4 or 8 × RTX 5090 / 4090✓ Only the GPU count changes: open your scene and render the way you do at home
Same on both machinesTip: upload the full project folder with relative paths so textures are found

How to read the figure. The left box is your own workstation and the right box is the iRender server: the same desktop, Blender version, add-ons and preferences, including Auto Depth and Zoom to Mouse Position once you set them there. The only difference is the GPU count, from 1 to 8 RTX 5090 or RTX 4090, which keeps the viewport and Cycles previews responsive on scenes that are slow at home.

  1. Upload first. Put the project in iRender Drive before you start a server; transfer and storage are free and no rental time runs while you upload.
  2. Start a server with 1, 2, 4 or 8 RTX 4090 (24 GB) or RTX 5090 (32 GB) GPUs. Multi-GPU servers bill per minute; 1-GPU servers have a one-hour minimum.
  3. Install Blender from blender.org (it is not pre-installed) and set your navigation preferences once; they stay in your server image.
  4. Set up the shot in the viewport, then render a test frame through the camera.
  5. Render the range, download the frames and shut the server down so billing stops.

Frequently asked questions

1. Why can’t I zoom in any further in Blender?

The view zooms toward a pivot point and each step covers a share of the remaining distance, so it slows down at the pivot. Select the object and press Numpad . to move the pivot to it.

2. How do I reset the view in Blender?

Press Home (View › Frame All) to fit the whole scene, or select an object and press Numpad . (View › Frame Selected) to center on it.

3. How do I zoom to the mouse cursor in Blender?

Open Edit › Preferences › Navigation and turn on Zoom to Mouse Position under Zoom. Turning on Auto Depth under Orbit & Pan helps as well.

4. How do I move through the scene past the zoom limit?

Use Dolly View with Shift+Ctrl+middle mouse, or Walk Navigation with Shift+` and the W, A, S, D, Q and E keys.

5. Why does my model disappear when I zoom in close?

The view is clipping it. Press N, open the View tab and lower Clip Start, keeping the range between Clip Start and Clip End no larger than the scene needs.

6. Does orthographic view have zoom stops?

No. In orthographic view zoom changes the scale of the view instead of moving it toward the pivot. Toggle between perspective and orthographic with Numpad 5.

Render your Blender projects on iRender

iRender is an IaaS GPU render farm: you rent a bare-metal server with 1, 2, 4 or 8 NVIDIA RTX 4090 (24 GB) or RTX 5090 (32 GB) GPUs, an AMD Ryzen™ Threadripper™ PRO CPU, 256 GB ECC RAM and a 2 TB NVMe SSD, connect by remote desktop and work on it like your own workstation, with full administrator access. You install Blender once; your server image is saved between sessions, so Blender and your add-ons stay installed.

Multi-GPU servers are billed per minute (1-GPU servers have a one-hour minimum), and sessions of 3 hours or more get 10% off. Our 4-GPU and 8-GPU servers are liquid-cooled; in our own measurements the GPUs hold 60–70°C under sustained render load. Elite support is available 7 days a week by hotline, live chat, Skype, WhatsApp and email.

This quick start shows how to start a server and render Blender on it:

Two Blender runs we recorded on our servers: 120 frames at 1080p on 4x RTX 5090 at 72 seconds per frame, and the same 4K scene on 4x RTX 5090 and 4x RTX 4090 at 87 and 108 seconds per frame per GPU:

New users get a 100% bonus on the first top-up (minimum $50). See plans on the Blender render farm page or download the iRender GPU app.

Accelerate your production pipeline with high-performance IaaS render farm services and dedicated bare-metal workstations powered by up to 8x NVIDIA GeForce RTX 5090 (32GB GDDR7), high-frequency AMD Ryzen™ Threadripper™ PRO processors, 256GB ECC RAM, and dedicated 2TB NVMe SSD storage tailored for your pipeline:
, , , , , , , , , , , , , , , , , , , , , ,

Jun Do

Learn something new everyday with iRender
Contact

iRENDER GPU

Render Farm Pricing
Quick Start
Multi-GPU Benchmarks
iRender GPU App
Blog
Documentation
The Render Farm
The Company
Terms & Conditions

INTEGRATIONS

Autodesk Maya
Blender
Cinema 4D
Houdini
Karma XPU
Lumion
KeyShot
Unreal Engine
Twinmotion
Redshift
Octane
And many more…

iRENDER TEAM

Elite support 7 days a week
SATURDAY – SUNDAY: 6:00 AM – 11:59 PM
(UTC+7)
Hotline: (+84) 912-785-500
Skype: iRender Support
Email: [email protected]
Address 1: 68 Circular Road #02-01, 049422, Singapore.
Address 2: No.22 Thanh Cong Street, Hanoi, Vietnam.

Contact
이 페이지는 한국어로도 제공됩니다. 한국어로 보기 →