AttributeError: ‘Options’ Object Has No Attribute ‘Img2Img_Editor_Height’ | Fixes That Stick

Guide / By

The img2img_editor_height error comes from a missing or misnamed setting or a bad extension; refresh configs, update WebUI, and disable the culprit.

When Stable Diffusion WebUI throws AttributeError messages tied to options, it’s usually a mismatch between the app’s expected settings and what your local files or extensions provide. The specific string here points to the editor height used in the img2img tool. In current builds, the option lives under the lowercase key img2img_editor_height. If an extension or an older fork asks for a different spelling—like the mixed-case Img2Img_Editor_Height—the app can’t find it and raises an error. The good news: you can fix it fast without reinstalling your whole stack.

AttributeError: ‘Options’ Object Has No Attribute ‘Img2Img_Editor_Height’ — Root Cause

This error pops up when the runtime tries to read a config attribute that doesn’t exist on the Options object. In modern AUTOMATIC1111, the valid key is img2img_editor_height in settings/config. A script or extension requesting Img2Img_Editor_Height won’t match. It can also appear after updates that regenerate config files while an extension expects the older shape. You’ll often see similar Options attribute errors with other keys when an extension falls behind a core change.

Quick Checks Before You Tinker

  • Restart WebUI — Close the terminal and browser tab, then relaunch. Temporary state can mask real fixes.
  • Update To Latest WebUI — Pull the newest AUTOMATIC1111 build so core option names and UI pieces are current.
  • Start With Extensions Disabled — Launch once with third-party add-ons turned off. If the error vanishes, an extension is the trigger.
  • Open A Clean Browser Session — Hard refresh or use a private window to avoid stale UI config cached by the browser.

Fix 1: Regenerate The Config Files Safely

Goal: get back a clean set of config files that include the img2img_editor_height key. WebUI keeps two important JSON files in the root folder: config.json and ui-config.json. If either is corrupted or missing keys, option lookups fail.

  1. Shut Down WebUI — Close the app so files aren’t in use.
  2. Back Up Configs — Copy config.json and ui-config.json to a safe spot.
  3. Delete The Originals — Remove config.json and ui-config.json from the WebUI root folder.
  4. Relaunch WebUI — The app writes fresh files with current keys, including img2img_editor_height.

Quick check: after relaunch, open Settings → User Interface and confirm the editor height renders normally in img2img. If the error is gone, you were missing or mis-shaped keys.

Fix 2: Correct A Misnamed Option In An Extension

Extensions sometimes call outdated attribute names. If your logs mention a specific extension file on the traceback, you can patch it in seconds.

  1. Locate The Failing Script — In the console stack trace, find the path under extensions/... that triggers the error.
  2. Search For The Wrong Key — Open the file and search for Img2Img_Editor_Height or any camel/pascal-cased variant.
  3. Swap To The Current Key — Replace with img2img_editor_height.
  4. Save And Reload UI — Use the WebUI’s Reload UI button or restart to apply.

Deeper fix: check the extension’s repo for updates that already align with current WebUI settings. When a maintainer ships a fix, prefer updating over a local patch to avoid drift.

Fix 3: Update Or Remove The Problem Extension

Many Options attribute errors are extension-driven. Narrow it down by toggling add-ons.

  • Disable All Add-Ons — Use the Extensions tab or temporarily move the extensions folder out of the WebUI root.
  • Add Back One-By-One — Restart and test after each add-on to catch the first failure.
  • Update From Source — Pull the latest version of the offending extension; changelogs often include option-name updates.
  • Replace The Extension — If the project is abandoned, switch to an actively maintained alternative that supports current releases.

Fix 4: Set Editor Height In Settings Or Manually

You can set the editor height through the UI or by editing the UI config file directly.

  • Use The UI — Go to Settings → User Interface, look for the image editor height option for img2img, apply a value like 720, then Apply settings and Reload UI.
  • Edit ui-config.json — Open ui-config.json in the WebUI root and confirm a line like "img2img_editor_height": 720. Save, then restart.

Note: the UI config also holds defaults for width, height, and step sizes in the img2img section. If your sliders don’t show expected ranges, adjust the related entries there and relaunch.

Fix 5: Clean Cache And Verify Browser Impact

The interface persists some state in the browser. An out-of-date cache can mask or prolong a config mismatch.

  • Hard Refresh The Page — Force a reload so scripts pick up the new keys.
  • Try A Private Window — Launch the WebUI URL in an incognito session to rule out stale cached assets.
  • Switch Browser — If the issue lingers in one browser, test another to confirm it isn’t a client quirk.

Fast Triage: Symptoms, Causes, And Fixes

Symptom Likely Cause Fast Fix
AttributeError mentions Img2Img_Editor_Height Extension calls an old key Patch to img2img_editor_height or update extension
Error vanishes with extensions off Third-party add-on mismatch Update or remove the add-on; keep core up to date
Fresh install still fails Corrupted or stale configs Delete config.json and ui-config.json; relaunch

Good Housekeeping To Prevent Recurrence

  • Update On A Schedule — Pull WebUI changes in batches and read the release notes before updating busy extension stacks.
  • Backup Configs — Keep copies of config.json and ui-config.json so you can roll back cleanly.
  • Avoid Mixed Forks — Don’t mix extensions built for different forks unless the author states compatibility.
  • Pin Known-Good Versions — For production work, pin WebUI and extensions to versions you’ve tested together.

When You Still See It After Fixes

If the message persists, copy the full stack trace and scan the topmost files listed. You’re looking for the first extension or script that references the wrong attribute. Replace the name in that file or remove the extension, then relaunch. If the trace points only to core files and you’re fully updated, regenerate configs again and test with a brand-new venv to exclude a Python package conflict.

Where The Setting Lives In Healthy Installs

On current builds, you’ll find the editor height key in plain lowercase. You might see it in WebUI configs and sample repos as:

"img2img_editor_height": 720

That spelling is what the Options object expects. Any extension using camel case for this key should be updated. After aligning names, the error string AttributeError: ‘Options’ object has no attribute ‘Img2Img_Editor_Height’ should disappear for good.

Bottom Line

A clean config set, current WebUI, and aligned extension keys resolve this fast. If you encounter AttributeError: ‘Options’ object has no attribute ‘Img2Img_Editor_Height’ again later, repeat the config refresh and extension check. It’s almost always a naming mismatch or a stale add-on.