Deriv bot XML won't import? What each error means and how to fix it

You have a Deriv bot XML file, you chose Import a bot, and instead of blocks you got an error, or nothing at all. BinaryTick's Bot Builder reads the same block format as Deriv's DBot, so most files load as they are. When one does not, the message points to the cause.

"Unsupported file format. Please import a valid XML file."

The importer checks the file name first, and only accepts a name that contains xml in lower case, such as my-bot.xml. A file named Bot.XML is turned away too, so rename it to lower case.

If you drag a file onto the import area and nothing happens at all, it failed this same check. Choose the file with the select button instead and you will see the message.

The usual causes:

• The bot arrived zipped. Many shared bots come as a .zip. Extract it first, then import the .xml inside.
• The download lost its extension. Some phones and messaging apps save files as .txt or with no extension at all. Rename the file to end in .xml.
• You picked the wrong file. A screenshot, a PDF guide or a text file of settings often travels alongside the bot. Look for the one ending in .xml.

"Your import failed due to an invalid file. Upload a complete file in XML format."

The file has the right name, but its contents are not a complete strategy. The importer rejects a file when the XML cannot be read, when it contains no blocks, or when it uses blocks the builder does not recognise.

The usual causes:

• An incomplete download. If a download was cut short, the end of the file is missing. Download it again and check that the file size looks right.
• A web page saved as XML. Some share links open a preview page, and saving that page gives you HTML with an .xml name. Open the file in any text editor. A real bot has <xml near the top and is mostly lines containing <block. If you see <html or <!DOCTYPE, go back and download the raw file.
• An older Binary Bot file. Early Binary Bot versions chose the market and the trade type with legacy blocks that the builder cannot convert. The importer drops those, finds nothing left, and shows this message even though the file is complete. Rebuild the strategy, as described below.
• Blocks from another platform. Files built in tools that add their own custom blocks will not load here either, and there is nothing to repair in the file itself. Rebuilding is the way forward.

Rebuilding a strategy that will not load

The quickest way forward is to start from a bot that already works. Open the Bots page, find a bot that trades the same contract, choose Edit in Bot Builder, and change its rule to match the one in your file. Every bot's rule is explained under How it works, so you can see which one is closest before you open it.

When it loads slowly

Files exported from Binary Bot and other third party platforms are converted as they load, so the import window says they may take longer. Wait for the blocks to appear before you try again.

After it loads

Once the blocks are on the canvas, read the strategy before you run it: the market, the stake and any martingale, and the stopping rules. How to upload a Deriv bot XML walks through what to check. Then run it on your demo balance first.

If you would rather skip the file altogether, every bot on the Bots page is free, explains its rule on its card, and has its limits set before you press Run bot.