When I try to place multiple images at once using the Gritify tool, my InDesign seems to break. It stops letting me undo, I can’t make any new files, it's constantly loading and it wont let me close the program anymore. Any way to stop or circumvent this?
That definitely doesn’t sound normal behaviour Gridify placing multiple images shouldn’t lock up the entire application like that.
A few questions first so people can narrow it down properly:
What are your full system specs? (RAM, CPU, available disk space, GPU)
What version of Adobe InDesign are you running?
What version of your operating system?
Are you running any third-party apps in the background (VPN, antivirus, system cleaners, cloud sync tools, font managers, etc.)?
When InDesign stops allowing Undo, won’t create new documents, and won’t close properly, that usually suggests one of the following:
A plugin conflict
Corrupt preferences
Memory pressure / scratch disk issue
GPU or display driver issue
OS-level interference
A few things you can try:
1. Reset InDesign Preferences
Corrupt prefs can cause exactly this type of behaviour. Hold Ctrl+Alt+Shift (Windows) or Cmd+Ctrl+Option+Shift (Mac) immediately after launching InDesign and confirm you want to reset preferences.
2. Start in Safe Mode
Boot your system into safe mode and launch InDesign without other startup services running. If Gridify works normally there, you know something local (background app, security software, font manager, etc.) is interfering.
3. Disable GPU Performance
Go to Preferences > GPU Performance and turn it off. Some rendering issues can cause freezes when placing multiple linked images.
4. Check Scratch Disk & Free Space
Make sure you’ve got plenty of free space on your scratch disk (ideally 20–30GB free). If InDesign runs out of working space mid-process, it can hang badly.
5. Test Without Gridify
Try placing multiple images manually using the standard Place command to confirm whether it’s specifically Gridify causing it. If it is, check:
Is it updated to the latest version?
Does the issue happen in a brand new blank document?
Does it happen with smaller image files?
If you can post your specs and versions, it’ll help pinpoint whether this is likely a compatibility issue, resource bottleneck, or a local conflict.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
AdChoices