Find metadata fast
Search common Salesforce metadata types instead of hunting through a long list.
FREE SALESFORCE DEVELOPER TOOL
Salesforce Package XML Generator
Build, import, merge, and compare Salesforce metadata manifests. Preview your package.xml and create destructive changes ZIPs all in your browser, with no Salesforce login.
✓ Live preview✓ Bulk paste✓ No login required
Manifest workspaceConfigure your deployment package
Runs locally in your browser
01
0 selected
Select metadata
02
Component names
Generate a package.xml for retrieving or deploying selected metadata.
Enter component names
One name per line, or separate names with commas. You can paste a whole list at once.
No metadata types selected
Select one or more types above to add their members.
Destructive changes can permanently delete metadata when deployed. Review every selected member before using these files.
Your input stays in this browser. Nothing is uploaded to a server.
MADE FOR SALESFORCE DEVELOPERS
From component names to package.xml
A simple workflow for preparing a Salesforce metadata deployment manifest.
Paste names in bulk
Add multiple Apex classes, flows, permission sets, or other component names at once.
Preview and download
Review the generated XML, copy it, or download a ready-to-save package.xml file.
This tool checks manifest structure and common issues locally. It cannot confirm that components exist in your org or guarantee deployment success.
FOR SALESFORCE ADMINS & DEVELOPERS
Meet Salesforce Companion
Your productivity sidebar for Salesforce
Spend less time navigating Setup and more time getting things done. Find fields and API names, generate SOQL queries, jump to frequently used tools, and identify your Salesforce environment—all from a handy sidebar inside Salesforce.
Instant field searchFind objects, fields, and API names quickly.
SOQL generatorBuild queries for the current record.
Quick navigationOpen Setup tools and Developer Console faster.
Environment awarenessKnow when you're in Production, Sandbox, or Developer Edition.
HELP & GUIDANCE
Frequently asked questions
Quick answers for creating and using Salesforce metadata manifests.
What if I can’t find a metadata type?
You can add a metadata type entry to the XML after generation. Use the exact API name documented by Salesforce’s Metadata API and follow the structure of the other <types> entries. Confirm that the type is supported by your selected API version.
Which API version should I select?
Use the version your project or deployment workflow targets. If your project has an sfdx-project.json file, its sourceApiVersion is a useful reference. Older versions may not support newer metadata features.
Does this website connect to my Salesforce org?
No sign-in or org authorization is required. Your selections and XML are processed in your browser and are not sent to a Salesforce org by this tool.
Does validation guarantee deployment will succeed?
No. Local checks can catch common issues, but cannot confirm component existence, org permissions, dependencies, or all Salesforce deployment rules.
What is a destructive changes manifest?
It identifies metadata to delete rather than retrieve or deploy. Deletion workflows have additional deployment requirements; review Salesforce’s current deployment documentation and carefully inspect every member before use.
What does the ZIP download contain?
Package mode includes package.xml. Destructive changes mode includes package.xml and destructiveChanges.xml using the selected API version.
Why is a component missing from the XML?
Only selected metadata types with component names are included. Check that the correct type is selected and that names are entered in its matching field.
Is my XML uploaded or stored?
Manifest generation and ZIP creation run locally in your browser. This tool does not upload your manifest to a backend. Your organization may still have policies about accessing unapproved websites.
Can I import an existing package.xml?
Yes. Use Import & Merge to choose an existing package.xml. The tool previews the imported members and merges them with your current selections after you confirm.
Will importing a package.xml create duplicate members?
No duplicate type/member entries are added. If the same member is already selected or appears more than once in the imported manifest, the merged output keeps one entry.
What happens to metadata types this generator doesn't display?
The importer reports unsupported types. The tool is designed to preserve valid imported entries in the generated manifest where possible; review the import summary before applying the merge.
Salesforce Developer Guide
Want to learn more about package.xml?
Explore our quick guide with a practical XML example and tips for building Salesforce metadata manifests.
Read the package.xml Guide