Do I download Dalamud separately?
Most XIVLauncher users receive Dalamud through the launcher workflow; avoid random standalone downloads.
Plugin framework context
Dalamud Launcher for FFXIV: What XIVLauncher Includes
Many people search for a Dalamud launcher when they mean XIVLauncher with Dalamud plugin support. This guide explains the relationship, the normal setup path, and the safety boundaries around third-party plugins.
What is Dalamud?
Dalamud is the plugin framework used with XIVLauncher. XIVLauncher handles the custom FFXIV launch flow, while Dalamud makes it possible for community-created plugins to run in game. That is why searches for dalamud launcher, ffxiv dalamud launcher, and ff14 dalamud launcher often point back to XIVLauncher.
What Dalamud is not
Dalamud is not the official Square Enix launcher, not an official plugin marketplace, and not a guarantee that every community plugin is safe or compatible with every game patch. Plugins are third-party code. Treat them like browser extensions or mod tools: install less, update carefully, and remove anything you do not understand.
XIVLauncher and Dalamud compared
| Component | Main role |
|---|---|
| XIVLauncher | Custom launcher and update flow |
| Dalamud | Plugin framework loaded with XIVLauncher |
| Plugins | Optional community extensions |
How to install and update Dalamud
Do not look for a random standalone Dalamud installer. For the usual Windows workflow, start with XIVLauncher, confirm the official project source, and follow its Dalamud flow. The exact menu or branch can change after a game patch.
If Dalamud stops loading after an FFXIV update, first test with plugins disabled and check the official project notes. Reinstall only after checking the launcher, plugin updates, and the relevant log or FAQ.
ToS and account risk
The official XIVLauncher site states that XIVLauncher is not in line with Square Enix ToS. Many users choose to use it, but the risk is still yours. This guide is informational and does not promise that any third-party launcher or plugin is risk-free.
Where to learn more
- Official XIVLauncher homepage for the project overview.
- Official FAQ for safety, antivirus, and troubleshooting topics.
- Dalamud GitHub repository for the plugin framework source.
How do I install Dalamud on FFXIV?
Use the supported XIVLauncher workflow and the official project documentation. Avoid downloading a separate DLL or installer from an unknown mirror.
How do I update Dalamud?
Keep XIVLauncher current, restart after an FFXIV patch, and check the official project notes if the framework or plugins are temporarily unavailable.
How do I reinstall Dalamud?
Try the launcher and plugin troubleshooting steps first. Reinstall only when the official guidance indicates it is necessary, and keep a backup of settings you understand.
Where is the Dalamud install folder?
There is no single path that fits every installation. Use the plugin-location guide and inspect the path configured by your own XIVLauncher setup instead of copying a random directory.
Is Dalamud a launcher?
No. XIVLauncher provides the launcher workflow, while Dalamud is the plugin framework used with it.
Can I use Dalamud without XIVLauncher?
The usual supported user path is through XIVLauncher and the official project documentation; avoid standalone DLL downloads from unknown sources.
What should I check after an FFXIV patch?
Test the base launcher first, check official compatibility notes, and keep unsupported plugins disabled until a supported update is listed.
Best next step
If your real goal is to download the launcher, start with the XIVLauncher download guide. If your real goal is choosing plugins, continue to the XIVLauncher plugins guide.
How Dalamud, XIVLauncher, and plugins fit together
XIVLauncher and Dalamud solve different parts of the same community workflow. XIVLauncher is the launcher and update path; Dalamud is the plugin framework that can be loaded through that launcher; plugins are optional community extensions. Treating these as separate layers makes troubleshooting easier. A launcher failure, a framework compatibility issue, and a single plugin error should not all lead to the same reinstall command.
For a normal Windows setup, start with the official XIVLauncher project and its current documentation. Do not search for a random standalone Dalamud installer or a DLL mirror. The supported menus, folder paths, and compatibility rules can change with FFXIV updates, so current project notes are more reliable than an old screenshot. Keep the launcher source and the plugin source visible before you run anything.
When a plugin is enabled, test the base path first. Launch the game without new plugins, confirm login and a normal zone change, then enable one extension and repeat the check. This gives you a useful boundary if the game closes, the UI becomes unstable, or the launcher reports an update problem. It also prevents a long list of simultaneous changes from hiding the first cause.
After an FFXIV patch, Dalamud or individual plugins may wait for an API update. An unavailable listing is not proof that the installation is corrupt. Check the official release and troubleshooting notes, leave unsupported plugins disabled, and avoid custom repositories that you cannot verify. If you must repair a local installation, keep settings you understand and record the step that changed the result.
Privacy and account safety still apply inside a third-party framework. Never provide a password, one-time password, session token, or payment detail to a plugin. Review logs before sharing them because chat, character, file, or account information can appear in diagnostic output. If a plugin's data behavior is unclear, do not enable it simply because another player recommends it.
Use the focused pages on this site for the next decision: the download guide covers the Windows release source, the plugin guide covers discovery, and the troubleshooting pages cover launcher, patch, and missing-plugin symptoms. Dalamud is a framework context, not a replacement for Square Enix support or a guarantee that community code is safe.
A practical Dalamud decision checklist
Before opening a plugin menu, name the layer you are trying to fix. Use the download page for a missing installer, the launcher troubleshooting page for a process that will not start, the patch guide for a download error, and the plugin guide for discovery. This simple boundary prevents a Dalamud question from turning into an unnecessary game reinstall.
Keep a small change log when you experiment: the release you tested, whether plugins were disabled, and the first screen that failed. You do not need to publish private logs. A short local note is enough to compare a clean launch with one plugin enabled and to give official support a precise description if you need it.
The safest default is reversible progress. Use the official project page, change one setting, test a normal session, and keep a clear way back. That approach is slower than copying a random fix, but it protects your files and makes the next Dalamud update easier to understand.
If you are unsure which page applies, describe the last visible state rather than guessing a component name. A launcher that never reaches login, a game client that closes after Play, and a plugin window that fails to load are different reports and should stay separate.
When you compare advice, keep the product boundaries visible: Dalamud is the plugin framework, XIVLauncher provides the supported launcher flow, and FFXIV remains the game client. Recording which layer produced the last visible message makes later troubleshooting shorter and reduces the temptation to replace files that were never involved in the failure.