Quick answer: If Hugin fails only on some projects, look at the folder names: parts of Hugin’s toolchain can choke on paths containing non-ASCII characters — accents (é, ü, ñ), Cyrillic, CJK and similar. The fix is unglamorous and total: move the photos and the .pto project into a plain-ASCII path such as C:\pano\, point Hugin’s temp directory at a plain path too, and the errors stop. More fixes on the troubleshooting hub.
Why a folder name can break a stitch
Hugin itself is a modern GUI application that handles international characters in filenames reasonably well. But Hugin is a front end: behind it sits a chain of command-line tools — CPFind, Nona, Enblend, Enfuse and others — that receive your file paths as text arguments. As the project’s own FAQ acknowledges, parts of this toolchain can mishandle paths containing characters outside plain ASCII, especially on Windows, where legacy code pages enter the picture. The result is a tool reporting that a file ‘cannot be opened’ or simply not found — even though the file is right there and Hugin itself displays it happily.
The failure pattern is diagnostic: the same photos stitch fine from one folder and fail from another; errors mention a filename rendered with garbled characters (the classic mojibake of an é turned into two strange symbols); or the project works until the final blend, when the last tool in the chain trips over the output path. If any of that sounds familiar, you are in the right guide. (If the blend fails on every project regardless of folder, it is more likely the cache or disk issue in our Enblend errors guide.)
The fix: give the project a plain-ASCII home
Do this once, in full — partial moves leave the one path that still breaks it:
- Create a plain folder at a short, simple location:
C:\pano\is ideal. No spaces are strictly fine either way, but short and simple removes all doubt. - Copy all the source photos for the project into it (copy, don’t move, until the stitch succeeds).
- Open the project in Hugin, relink any photos it cannot find to the copies in
C:\pano\, and Save the project (.pto) into the same folder. - Stitch, and set the output file to the same folder as well, with a simple name like
panorama.tif.
All four paths — images, project, temp (next section) and output — must be clean. Users often fix the photos and forget the output, then watch the blend fail at 95% on the very last write.
Do not forget the temp directory
Hugin and Enblend write large intermediate files to a temp folder, and by default that is your system temp location — which lives under your user profile. If your Windows username itself contains an accented character, your temp path contains one too, and every project inherits the problem even from a clean folder. In Hugin’s Preferences you can set the temp directory explicitly: point it at C:\pano\temp\ (create the folder first). This single setting is the whole solution for users whose names contain accents — see the next section.
The username trap
This bug bites hardest where it is least expected: people whose own name contains an accent — José, François, Björn, Łukasz — and whose Windows or macOS account was created with it. Then C:\Users\José\Pictures\... is a non-ASCII path by default, and every photo stored in the standard libraries is already in ‘problem’ territory before Hugin is even installed. The same applies to Cyrillic, Greek, Chinese, Japanese and Korean usernames. If that is you, adopt the habit permanently: keep a plain C:\pano\ working folder for stitching projects, and set the temp directory once as above. You do not need to rename your account.
Keep filenames simple, too
Folder names are the usual culprit, but filenames can carry the same characters. Camera files (DSC_0123.jpg) are always safe; the risk arrives when photos are renamed descriptively in your language, or pass through phones and messaging apps that rewrite names. For stitching work, keep names to letters, digits, hyphens and underscores. Renaming copies for the pano folder — img01.jpg, img02.jpg… — is a two-minute insurance policy, and your originals stay untouched. Relatedly, when the failure message names a missing file that visibly exists, treat it as this bug until proven otherwise. And if a project fails in a plain path too, the cause is elsewhere: start at the troubleshooting hub or the optimizer errors guide.
How to spot it in the error output
Hugin’s stitch log is your evidence. When a path is the problem, the failing line usually shows the filename damaged: accented letters replaced by two-character gibberish, question marks, or boxes — the visible signature of an encoding conversion gone wrong between the GUI and the command-line tool. Compare that mangled name with the real folder name and the diagnosis makes itself. A second tell is which stage fails: alignment inside Hugin’s own code may succeed while an external helper — the blender, the exposure fuser, the control point generator on some builds — reports the file missing. Stage-specific failure plus a garbled filename in the log equals path trouble, virtually every time. Conversely, if the log shows clean, correct filenames and a memory or ‘failed’ message, leave the paths alone and look at resources instead — our Enblend errors guide covers that branch.
FAQ
Which characters count as ‘non-ASCII’ here?
Anything beyond the basic English letters, digits and common punctuation: accented letters (é, ü, ñ, ç), ß, Cyrillic, Greek, Hebrew, Arabic, Chinese, Japanese and Korean characters, emoji, and typographic quotes. Plain a–z, 0–9, hyphen and underscore are always safe.
My photos are in OneDrive or Dropbox. Does that matter?
It can: cloud folders often live under your user profile (inheriting an accented username), and sync tools sometimes present placeholder files that command-line tools cannot read mid-sync. Copying the photos to a local plain path like C:\pano\ removes both variables at once.
Does this bug exist on Mac and Linux too?
Linux toolchains generally handle UTF-8 paths well, and macOS sits in between; the problem is most reported on Windows because of code-page conversions between the GUI and the tools. The plain-path habit is cheap insurance on any system if you hit unexplained file errors.
Will renaming folders break my existing .pto projects?
A .pto stores the paths to its photos, so moving or renaming means Hugin will ask to relink them. That is painless: open the project, point each missing photo at its new location once, and save. Keeping copies (not moves) until the stitch works avoids any risk.
