Category: Others

Let’s be honest Photoshop in 2026 is a beast. Every AI feature Generative Fill, Content-Aware, neural filters it all ships with default settings tuned for a workstation, not your actual machine. photoshop and graphic_design communities have been screaming about this for two years straight, and they’re right.

The good news is that most of the lag isn’t your hardware’s fault. It’s misconfigured settings, bloated scratch disks, and AI layers quietly recalculating in the background. Here’s how you fix all of it, in order.

1. The Performance Preference Overhaul

This is your first stop. Go to Edit → Preferences → Performance and prepare to undo everything Photoshop decided for you by default.

Memory Usage, find your sweet spot. Photoshop defaults to a conservative memory allocation, but the real target is 70–85% of your available RAM. If you’re on 16GB, that means giving Photoshop roughly 11–13GB. The slider is right there drag it, and your canvas will thank you immediately.

Graphics Processor settings need attention too. Enable Use OpenCL under Advanced Settings it offloads sharpening and blur filters to your GPU rather than your CPU, which is dramatically faster. If you’re on an older GPU or an M1/M2 Mac and experiencing crashes, toggling Legacy GPU Mode on is the Reddit-recommended fix that quietly solves a lot of “unexplainable” instability.

History States is where most people leave performance on the table. The default is 50 states, which sounds useful until you realise Photoshop is storing every single undo step in RAM. Drop it to 20 you rarely need more than that, and the RAM you free up is significant on complex files.

Cache Tile Size is the setting nobody explains properly. If you work with large, flat files and few layers (photography, composites), use Large Tiles they process big chunks faster. If you work with many layers, masks, and text (design, illustration), use Small Tiles they handle frequent, small changes more efficiently. Match your tile size to how you actually work.

2. Scratch Disk Strategy

Your scratch disk is Photoshop’s overflow when RAM fills up, everything spills here. If that overflow destination is slow, your whole workflow grinds. This is the number one cause of the mid-session freeze that feels like Photoshop is “thinking” when it should just be doing.

Never use your OS boot drive as your primary scratch disk. Your C: drive is already handling Windows or macOS system processes, app data, and page file management. Stacking Photoshop’s overflow on top of that creates a bottleneck that no amount of RAM can fix.

The external NVMe SSD trick is legitimately excellent. A dedicated NVMe drive connected via Thunderbolt 4 or USB4 gives you near-internal speeds as a scratch disk. Assign it in Preferences → Scratch Disks, move it to the top of the list, and you’ve essentially given Photoshop a high-speed overflow lane at a fraction of the cost of upgrading your internal storage.

Keep at least 15–20% of your scratch disk free at all times. When a drive approaches capacity, read/write speeds drop sharply the “Your scratch disk is full” error is just the visible end of a problem that starts much earlier. Set a calendar reminder to clear your scratch disk monthly if you’re doing heavy work.

3. Optimizing the Workflow The “UI Tax”

Every visible element in Photoshop costs something. Rulers, guides, open panels, active artboards they all consume CPU cycles quietly in the background. None of them are expensive individually, but together they add up to a slower, heavier canvas experience.

The “Hide to Speed Up” list is short and worth memorising. Turn off Rulers with Ctrl+R, hide Guides with Ctrl+;, and collapse or close any Artboard panels you’re not actively using. These are one-keystroke habits that collectively reduce canvas rendering load especially noticeable on lower-end machines or when zooming in and out of large files.

Close the Learn and Libraries panels if you’re not using them. This one surprises people both panels actively ping Adobe’s servers to check for content updates, which eats bandwidth and CPU in the background. Right-click and close them. You can always reopen them when needed.

Brush Smoothing is the most overlooked cause of brush lag. Photoshop defaults to some level of smoothing, which means every stroke is being calculated and corrected in real time. Set it to 0% for standard work it eliminates the slight delay between your stylus and the stroke, making the whole painting experience feel immediate and responsive again.

4. Dealing with AI & New Features

Generative Fill is the most resource-hungry feature in Photoshop right now. Every AI-generated layer retains its metadata so Photoshop can re-generate or adjust it later but if you’re done with the result, that’s just dead weight. Rasterize your Generative Fill layers once you’re satisfied: right-click the layer → Rasterize Layer. It converts the AI layer to a normal pixel layer and stops Photoshop from recalculating it every time you scroll or zoom.

“Always Save to Cloud” has a real performance cost. Every time Photoshop auto-saves, if cloud sync is enabled, it’s uploading your file in the background and on large PSDs, that’s a significant background task. Switch to local saving in Creative Cloud preferences and manually sync when you’re done for the day. Your mid-work experience will be noticeably smoother.

Content-Aware features can quietly slow down large libraries. If you have a large Creative Cloud Libraries collection, disabling background index searching stops Photoshop from querying your library assets while you work. Go to Libraries → Settings and turn off “Sync with Creative Cloud” temporarily during intensive sessions turn it back on when you’re done.

5. File Handling & Background Tasks

Disable PSD Compression and accept the trade-off. By default, Photoshop compresses PSDs to save disk space — but compression and decompression on every save and open is a real CPU cost. In Preferences → File Handling, uncheck “Maximize PSD and PSB File Compatibility.” Your files will be larger, but opening and saving will be noticeably faster, especially on SSDs where storage space is less of a concern than processing overhead.

Auto-Save every 5 minutes sounds safe until you’re mid-stroke. The default 5-minute auto-save interval triggers a background write process that causes that familiar “freeze-stutter-resume” cycle. Change it to every 15 or 30 minutes in Preferences → File Handling. For extra safety, just hit Ctrl+S manually whenever you finish a major step it’s faster than waiting for auto-save anyway.

Edit → Purge → All is the manual RAM reset you should be using regularly. During long sessions, Photoshop accumulates clipboard data, history states, and video cache that it doesn’t automatically release. Purging all of it mid-session clears that accumulated bloat without requiring a full app restart. Use it before starting a new document or switching to a significantly different task.

6. Maintenance & Troubleshooting (The Nuclear Options)

A corrupted preferences file causes more “unexplainable” lag than most people realise. Every major Photoshop update can leave preference conflicts that slow the app down in ways that don’t show up in any diagnostic. Hold Shift+Ctrl+Alt (Windows) or Shift+Cmd+Opt (Mac) at startup to reset preferences to factory state. It feels drastic, but it’s the single most effective fix for post-update performance degradation.

NVIDIA users should be on Studio Drivers, not Game Ready Drivers. Game Ready Drivers are optimised for frame rates and gaming workloads they can introduce instability in creative applications. Studio Drivers are specifically validated for Adobe software, and the difference in Photoshop stability (especially with GPU-accelerated features) is real and documented across Reddit threads.

Sometimes the right answer is rolling back a version. Adobe’s Creative Cloud app lets you install previous versions of Photoshop under the “Other Versions” option. If a recent update introduced lag you can’t fix through settings, rolling back one version is a legitimate and underused option. You’re not stuck with the current build.

One Peer Tip Worth Taking Seriously

If you’re regularly working with 100+ layers or large print files, the Reddit consensus in 2026 is increasingly pointing at Affinity Photo or InDesign as the speed-practical choice for those specific workflows. Photoshop is a resource glutton by design it’s built to do everything, which means it always carries overhead for the things you’re not using.

Knowing when to use the right tool for the task is itself an optimisation. Use Photoshop for what it does best, and don’t be afraid to route specific workflows through lighter alternatives. Your RAM will thank you.

If you’re running Chrome on 4GB RAM in 2026, you already know the pain. You open three tabs, your system fan starts screaming, and Google Maps turns your browser into a very expensive paperweight. Chrome’s everyday bloat has reached a genuine tipping point.

The frustrating part? Most of the lag is fixable without upgrading your hardware. Chrome’s default settings are tuned for machines with 16GB of RAM and fast SSDs. On a 4GB system, those defaults are actively working against you. Here’s how to change that.

First Understand What’s Actually Happening on Your Machine

Before touching a setting, open Chrome’s built-in Task Manager with Shift + Esc. You’ll immediately see something surprising Chrome isn’t one process, it’s dozens. Every tab, every extension, and every background service runs as a separate process, each with its own memory allocation. On 4GB RAM, this architecture is brutal.

The GoogleUpdater.exe problem is real and it’s the first thing you’ll notice. Opening Chrome in 2026 can trigger 7–8 simultaneous instances of GoogleUpdater in the background, causing CPU spikes up to 70% for the first few minutes of every session before you’ve even loaded a page. This isn’t a virus, it’s Chrome doing maintenance at the worst possible time.

“Zombie processes” are the invisible RAM drain nobody warns you about. When you close a tab, Chrome doesn’t always release the memory that tab was using. The process lingers in the background, consuming gigabytes of RAM long after you’ve moved on. On a 4GB system, two or three zombie processes can silently eat half your available memory and the system has no obvious way to tell you this is happening.

Here’s what that looks like on a real 4GB machine:

Total realistic RAM usage before you’ve done anything useful: 2.5–3.5GB on a 4GB machine. That’s the problem in a table.

Step 1 Kill the Startup CPU Spike

The first fix is stopping GoogleUpdater from running wild at launch. Open Task Manager (Ctrl + Shift + Esc), go to the Startup tab, and disable any Google Update entries listed there. Then navigate to C:\Program Files (x86)\Google\Update and rename GoogleUpdate.exe to GoogleUpdate.exe.bak — this prevents the updater from auto-launching without uninstalling Chrome entirely.

Chrome will still update just on its own schedule instead of every single launch. You can manually trigger updates by going to chrome://settings/help whenever you want to check. This one change alone can eliminate the 2–3 minute CPU freeze that makes Chrome feel broken every time you open it on a low-end machine.

Disable unnecessary startup background processes inside Chrome itself. Go to chrome://settings/system and turn off “Continue running background apps when Chrome is closed.” On a 4GB machine, Chrome running silently in the background while you’re doing other things is not a feature — it’s a resource thief. Turn it off completely.

Step 2 Enable Memory Saver and Configure It Properly

Memory Saver Mode is the single most important Chrome setting for 4GB RAM users and it’s off by default. Go to chrome://settings/performance and toggle Memory Saver to On. This puts inactive tabs to sleep — they stop consuming RAM and CPU until you click back on them, at which point they reload.

The difference on a 4GB machine is dramatic. With Memory Saver on, an open tab that you haven’t touched in five minutes drops from 200–400MB of active RAM usage to near zero. With 10 tabs open, that’s potentially 2–3GB of RAM returned to your system. Set it to “Maximum savings” mode if the option is available, the slight reload delay when switching tabs is absolutely worth it at this RAM level.

Add your most-used sites to the “Never sleep” exceptions list. If you keep Gmail or your work dashboard open constantly and hate the reload delay, go to Memory Saver settings and whitelist those specific sites. Everything else gets put to sleep only your actively-needed tabs stay warm. This is the balance that makes Memory Saver actually usable rather than just annoying.

Step 3 Deal with the Extension Problem

A single heavy extension can cause more lag than five extra open tabs. Reddit threads in 2026 have specifically called out Bitwarden and script-heavy adblockers as causing minutes-long startup lag on lower-end machines not because they’re badly made, but because they run persistent background scripts that Chrome can’t efficiently manage alongside everything else.

The fix isn’t to disable extensions it’s to audit them the same way you’d audit startup programs. Go to chrome://extensions and look honestly at what’s there. Anything you haven’t actively used in the past two weeks should be removed entirely, not just toggled off disabled extensions still load their service workers at startup on some Chrome versions. Removal is the only clean cut.

For password managers and adblockers specifically, reinstall rather than toggle if you’re experiencing lag. The current community-verified fix for extension conflict loops where one extension causes the browser to freeze on startup is a clean reinstall of the problematic extension rather than a disable/enable cycle. Corrupted extension data doesn’t clear on disable, but it does clear on uninstall. If Chrome is slow specifically at launch, this is worth trying before anything more drastic.

Keep your active extension count to five or fewer on a 4GB machine. That’s not a preference it’s a practical RAM budget decision. Use Shift + Esc to open Chrome Task Manager and check exactly how much RAM each extension is consuming. Anything above 100MB that you don’t use daily is a candidate for removal.

Step 4 Fix Hardware Acceleration (The Google Maps Problem)

Typing lag and browser freezing on Google Maps is almost always a Hardware Acceleration conflict. The latest Chromium builds have a known issue where Hardware Acceleration conflicts with newer GPU drivers particularly on integrated graphics, which is what most 4GB RAM machines are running. The result is input lag where letters appear seconds after keystrokes, stuttering video, and occasionally a full browser crash.

Try disabling Hardware Acceleration first and see if the problem disappears. Go to chrome://settings/system and toggle “Use hardware acceleration when available” to Off, then relaunch Chrome. If Google Maps suddenly works properly and the typing lag is gone, you’ve found your culprit. On integrated graphics with limited VRAM, software rendering is sometimes genuinely faster than a conflicted hardware acceleration path.

If you need Hardware Acceleration for video smoothness, update your GPU driver before re-enabling it. On Intel integrated graphics, go to Intel’s driver support site and grab the latest DCH driver. On AMD integrated (Ryzen APUs), use AMD’s auto-detect tool. An outdated driver combined with Chrome’s latest Chromium build is the most common cause of the acceleration conflict the fix is usually a driver update, not a permanent setting change.

Step 5 The Profile Reset (When Nothing Else Works)

If Chrome still lags after all of the above, the issue is almost certainly a corrupted profile cache. This is the fix that Reddit threads keep returning to in 2026 and the important distinction is that “Reset Chrome” in settings does not actually fix this. A settings reset leaves your profile data, extensions, and cached files intact. The corrupted data stays.

Create a completely new Chrome profile instead. Click your profile picture in the top right → Add → Create new profile. Sign in fresh on the new profile and reinstall only the extensions you actually need. In most reported cases, the new profile runs dramatically faster because you’re not carrying months of accumulated corrupted cache data that the standard reset ignores.

As a last resort before switching browsers, clear Chrome’s profile data manually from the file system. Close Chrome completely, navigate to C:\Users\[YourName]\AppData\Local\Google\Chrome\User Data\Default, and delete the Cache, Code Cache, and GPUCache folders. These rebuild automatically on next launch and are safe to delete they’re just stored website data, not your passwords or bookmarks.

The 4GB RAM Reality Check Table

Alternative Browsers Worth Considering

If Chrome remains unusable after all of the above, the community has two strong recommendations for 4GB RAM machines. Brave which is Chromium-based, so all your extensions work consistently reports 20–30% lower RAM usage than Chrome with its built-in ad blocking handling what extensions would otherwise handle. Microsoft Edge has the best “sleeping tab” implementation of any major browser, and on Windows it integrates with the OS in ways that make it genuinely more efficient on lower-end hardware.

Switching browsers isn’t giving up it’s using the right tool for your hardware. Chrome is excellent on 16GB RAM. On 4GB, Brave or Edge will give you a meaningfully better daily experience for the same browsing tasks, and both sync with your Google account so the transition is painless.

VS Code in 2026 is quietly becoming what it once made fun of a heavy, memory-hungry editor that slows down the longer you use it. Between GitHub Copilot pinging models in the background, GitLens indexing your entire commit history, and Electron doing what Electron does, what was once a “lightweight” editor now regularly tips past 1GB of RAM before you’ve even opened a file.

The good news is that almost all of it is fixable through your settings.json. Reddit’s developer communities have been documenting these fixes all through 2025 and 2026, and the consensus is clear the defaults are set for showcasing features, not for performance. Here’s how to take it back, in order.

1. Trimming the Bloat The Anti-Lag Strategy

Inline Suggestions is the single biggest cause of typing lag in 2026. Every keystroke triggers a background call either to a local model or a remote one and that constant pinging adds latency between your fingers and the screen. Open your settings.json and set "editor.inlineSuggest.enabled": false. You can still trigger suggestions manually with Ctrl+Space when you actually want them.

The 5-Extension Rule is the audit you’ve been putting off. Open the Extensions panel, sort by install count, and ask honestly: how many of these run all the time, not just when you call them? GitLens, Pylance, and ESLint all perform CPU-heavy “Code Actions on Save” if you’re saving frequently (which you should be), these are firing constantly. Audit down to five truly essential extensions and disable the rest globally.

Workspace-specific extension management is the habit that changes everything. Instead of running all your Python tooling globally, disable extensions at the global level and only enable them per workspace. Your Markdown project doesn’t need Pylance. Your HTML project doesn’t need a Rust analyzer. Go to any extension → right-click → “Disable (Workspace)” to start working this way immediately.

Clearing VS Code’s cache resets performance that degrades over weeks. After months of use, the global storage and workspace storage folders accumulate stale data that quietly slows the app. Close VS Code, navigate to %APPDATA%\Code on Windows or ~/.config/Code on Linux/Mac, and delete the contents of User/workspaceStorage it rebuilds cleanly on next launch and the difference is often immediately noticeable.

2. UI & Visual Performance Optimization

The VS Code UI runs inside Electron, which means every visual element has a GPU and RAM cost. The minimap, indent guides, whitespace rendering, and bracket decorators are all being redrawn constantly as you type and scroll. Stripping the ones you don’t actively use is the fastest way to reduce the editor’s visual overhead without touching functionality.

Add these to your settings.json and feel the difference:

"editor.minimap.enabled": false,
"editor.guides.indentation": false,
"editor.renderWhitespace": "none"

The minimap alone is one of the more expensive UI elements it re-renders a pixel-level view of your entire file on every change. Most developers never actually use it for navigation. Turning it off is a clean win.

Hardware acceleration is worth verifying not just assuming it’s on. VS Code uses GPU acceleration through Electron, but on some systems (particularly those with older integrated GPUs or certain Linux drivers), it can silently fall back to software rendering, which tanks performance. Open the Command Palette → “Configure Runtime Arguments” → check that disable-hardware-acceleration is not set to true. If it is, remove that line and restart.

3. Tweaking “Smoothness” — Fluid Navigation

Two settings that cost almost nothing but make VS Code feel premium to use. Add both to your settings.json:

"editor.cursorSmoothCaretAnimation": "on",
"editor.smoothScrolling": true

The smooth caret animation makes the cursor glide between positions instead of jumping it sounds cosmetic but it genuinely reduces the visual jitter that makes editing feel “snappy but rough.” Smooth scrolling on long files is similarly low-cost and high-impact.

Don’t turn off Quick Suggestions entirely tune them instead. Turning suggestions off globally removes a genuinely useful feature. The better fix is to limit where they fire and add a small delay so they don’t trigger on every single character:

"editor.quickSuggestions": {
  "other": true,
  "comments": false,
  "strings": false
},
"editor.suggestDelay": 10

This stops suggestions from firing inside comments and strings two places they’re mostly noise while keeping them active in actual code. The 10ms delay is imperceptible to you but enough to prevent suggestions from triggering mid-word.

4. Workflow Tricks for Speed

Running two VS Code windows for frontend and backend is costing you roughly 1GB of RAM. Each window is a separate Electron process with its own V8 heap, extension host, and language server instances. Use Multi-root Workspaces instead File → Add Folder to Workspace and keep everything in one process. It’s one of the most impactful RAM reductions you can make without changing a single setting.

VS Code’s integrated terminal gets significantly slower with heavy ZSH or Fish themes. Powerline fonts, git status decorators, and custom prompts all add execution overhead to every terminal command and inside VS Code’s terminal layer, that overhead compounds. Create a lighter shell profile specifically for the integrated terminal and keep your full-featured theme for your standalone terminal app.

The Command Palette should be your primary navigation tool, not the mouse. Every time you reach for the mouse to click a menu, you’re breaking your input-to-editor loop. Ctrl+Shift+P for commands, Ctrl+P for files, Ctrl+G for line numbers these three shortcuts handle 90% of navigation. The less your hands leave the keyboard, the tighter and faster your editing rhythm becomes.

Quick Settings Reference Table

One Pro Tip Worth Pinning

If you notice lag that gets progressively worse the longer you type in a session, it’s almost certainly a memory leak in a specific extension. This was widely reported with Copilot and Ruff in early 2026 not a VS Code core issue, but an extension host issue. Before you restart the entire app, try Ctrl+Shift+P → “Developer: Reload Window” it restarts the extension host and clears the leak in about two seconds, without losing your open files or editor state.

It’s faster than a full restart and fixes the problem just as effectively. Add it to muscle memory.