Skip to main content
Learn how to take templates from the marketplace and use them in your ComfyControl workflows. These curated templates are designed to help beginners get started with ComfyUI, from discovery to execution.

Using Marketplace Templates

Follow this workflow to successfully implement marketplace templates in your projects:

1. Browse & Discover

Search the marketplace for workflows that match your needs. Use categories, keywords, and filters to find the perfect template for your project.
Marketplace templates are curated for beginners to help you get started with ComfyUI. Advanced users may prefer building custom templates tailored to their specific needs.

2. Review Requirements

Check the template’s requirements section carefully before forking:
  • Required models: Download and install necessary AI models
  • Custom nodes: Install any ComfyUI custom nodes
  • Required VRAM: Ensure your hardware meets the minimum requirements
  • ComfyUI version: Verify your ComfyUI installation is compatible
  • Installation instructions: Follow setup guides provided
  • Sample outputs: Review examples to understand expected results
Skipping this step may result in workflow execution failures. Always verify you have all dependencies installed on your runners.

3. Fork Template

Create your personal copy of the template to modify and use in your workflows. Forking creates an independent copy that you can customize without affecting the original. Click the Fork button on any template page to add it to your personal template collection.
Forked templates appear in your personal templates section and can be modified freely.

4. Setup Dependencies

Install required models and custom nodes on your runners:
  • Download models to your ComfyUI models directory
  • Install custom nodes via ComfyUI Manager or manually
  • Verify installations are complete before executing workflows
  • Test dependencies on at least one runner
You’re responsible for managing AI models and custom nodes on your ComfyUI instances. ComfyControl does not automatically install dependencies.

5. Customize & Execute

Modify the forked template to suit your needs:
  • Adjust placeholder values for your use case
  • Fine-tune parameters and settings
  • Add or modify workflow nodes if needed
  • Execute the workflow on your runners
  • Monitor execution progress in real-time

6. Star & Share

Show appreciation for useful templates and help the community:
  • Star templates that work well for you
  • Rate templates to provide feedback
  • Help others discover quality workflows through your engagement
Community sharing coming soon! You’ll be able to share your customized templates with others.

Pro Tip

Always check the requirements section before forking a template. Make sure you have the necessary models and custom nodes installed on your runners to avoid execution failures. Remember that marketplace access requires login.

Community Features

Engage with the marketplace community through stars and forks.

Star System

Show appreciation for useful templates by starring them. Stars help other users discover helpful beginner-friendly workflows and provide feedback to administrators curating content. How to Star a Template: Click the star button on any template page to show your appreciation and help others discover quality content. Your stars contribute to the template’s overall rating and visibility in search results.
Starred templates are saved to your favorites for easy access later.

Fork System

Create personal copies of templates to modify and customize. Forks allow you to build upon existing work while preserving the original template. How to Fork a Template: Click the fork button to create your own copy that you can modify without affecting the original template. Your forked version becomes part of your personal template collection. Benefits of Forking:
  • Independence: Modify freely without affecting the original
  • Customization: Adapt templates to your specific needs
  • Version control: Maintain your own version while the original evolves
  • Learning: Study and learn from high-quality workflows
Fork counts are displayed on each template, showing how many users have found it useful enough to create their own copy.

Best Practices

Follow these guidelines for the best marketplace experience as you learn ComfyUI:

Before Forking

  • Read the complete template description
  • Review all requirements including VRAM and ComfyUI version
  • Check community ratings and fork counts
  • Review sample outputs to understand what to expect

After Forking

  • Test the template with default settings first
  • Document your customizations for future reference
  • Keep track of required models and custom nodes
  • Update your runners when templates have new dependencies

During Execution

  • Monitor the first execution closely
  • Verify outputs match expected results
  • Adjust parameters based on initial results
  • Save successful configurations for reuse
If a workflow fails to execute, verify that all dependencies are installed correctly on the runner that attempted to execute it.

Troubleshooting

Common issues and solutions when using marketplace templates:

Missing Dependencies

Problem: Workflow fails with missing model or custom node errors Solution:
  • Review the template’s requirements section
  • Install missing models in your ComfyUI models directory
  • Install missing custom nodes via ComfyUI Manager
  • Restart your ComfyUI runner after installations

Execution Failures

Problem: Workflow enters failed state during execution Solution:
  • Check runner logs for specific error messages
  • Verify all placeholder values are valid
  • Ensure the runner has sufficient resources (VRAM, RAM)
  • Test the workflow in ComfyUI directly to isolate issues

Wrong Outputs

Problem: Outputs don’t match template examples Solution:
  • Verify you’re using the same model versions
  • Check if random seeds are causing variations
  • Review parameter values against template documentation
  • Ensure custom nodes are up to date
Join the community discussions for templates you’re using. Other users may have encountered and solved similar issues.

Next Steps