Oh how I would love to love the Org Browser… it is meant to be so good. It is meant to be the fix for not having to hand build a package.xml file. Org Browser can STILL not download managed package metadata. So if you have for example, NPSP, and you’ve added a custom field onto the Affiliations object, you can’t download that object and your custom fields using the Org Browser. So it is almost basically useless. See the Issue that is still open.
Package.xml
Now, as we are not developers and want to see ALL our metadata we have to get our full package.xml file with the structure of our org.
You can code it by hand, but that is just boring. You could use another tool like Illuminated Cloud to build it but it’s still not easy. Here’s an example standard package.xml but check if it is what you need for your org and it’s not up to date with the latest things.
Here is the docs for package.xml https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/manifest_samples.htm
...