Update Solana NFT Metadata

Yes, directly. Upload the new image and save: we host it, rebuild the metadata file around it, and write the new link on-chain. The picture is not on-chain itself, so this is really two steps, but you only do one. If you host the metadata file yourself and would rather keep control of it, Advanced still takes a link you supply.

No. Traits live in the metadata file, and saving replaces that file rather than editing it, so the tool reads it first and writes every trait back unchanged. It tells you how many it found before you sign. The file list and animation are carried the same way, and if the current file cannot be read at all the tool says so and makes you confirm rather than quietly dropping what was in it.

No, and that is the reason this tool exists. The Metaplex instruction underneath replaces the whole metadata record rather than patching one field, so anything not restated is erased. This tool reads the current values first and writes back every field you did not touch, including the royalty rate, the creator list and the collection link.

No. Setting or verifying a collection is a different instruction, and it needs the collection authority to sign rather than the NFT's update authority. Offering it here would produce a transaction that fails after you had already approved it. The collection link is read, shown and preserved, never rewritten.

Because one of the creators is verified. A creator verifies themselves by signing, and the program then refuses to let anybody else adjust that entry, including the update authority. The list is displayed so you can check it, and it is preserved exactly as it is by anything you save.

Some will and some will not. The rate is a number in the metadata, not a rule the chain enforces: nothing about a transfer checks it. Most Solana marketplaces moved to optional or creator-set royalties, so treat this as what you are asking for rather than what you will receive. Setting it correctly still matters, because the marketplaces that do honour it read this field.

Exactly 100, not up to 100. The program refuses any other total outright, so a list summing to 99 is not a smaller royalty, it is a transaction that fails. The tool adds the shares up as you type and refuses to send until they balance.

Yes. A collection is itself an NFT with a metadata account, so the same instruction edits it and the tool says so when it detects one. Changing the collection NFT's own name and image is how the collection appears differently in wallets. It does not change the items inside it, which each have their own metadata.

No, and neither can anyone else. Immutable is permanent by design: it is the guarantee that an NFT someone bought cannot be swapped for something different afterwards. If the metadata was locked, the name, image, royalties and creators are fixed for good.

Only the wallet holding the update authority can edit an NFT, and that is not always the wallet holding the NFT. If you bought it, the creator almost certainly kept the authority. If you minted it through a launchpad, the authority may sit with that platform. The tool shows which address holds it so you can check whether it is one of yours.

No, and it refuses one up front rather than failing at the wallet popup. Token-2022 keeps metadata inside the mint rather than in a separate Metaplex account, and that format has no field for a royalty rate or a creator list at all, so there would be nothing here to edit.

They write the same account through the same instruction, and they differ in what they let you touch. Update Metadata handles the name, symbol and URI of a fungible token and restates royalties and creators as whatever they already were. This one is the only place those two are editable, which keeps the number of screens that can change who gets paid at exactly one.

The chain has it as soon as the transaction confirms. Wallets, explorers and marketplaces cache metadata and refresh on their own schedules, so a few minutes is normal and some marketplaces have a manual refresh button on the item's page.