When creating a project in UiPath Studio, you may see options for Process, Template, and Library. They all help you build automations, but each serves a different purpose.
The simple way to remember them is:
- Process: Build an automation that a robot can run.
- Template: Create a project structure that others can reuse as a starting point.
- Library: Create reusable workflows or activities that can be added to multiple projects.
What is a UiPath Process?
A Process is the automation project you build to complete a specific task. You design the workflow, add activities, and publish it so it can be run by a robot.
Example: Create a process that reads invoice details from email, enters them into an application, and saves the results.
Choose Process when you want to build and run an automation for a particular business task. docs.uipath.com
What is a UiPath Template?
A Template is a preconfigured project that developers can use as a starting point. It can include a project structure, workflows, dependencies, variables, and arguments.
Example: Create an invoice automation template with a standard folder structure and common workflows. Developers can create new projects from it and customize them for different clients.
Choose Template when you want to make it easier for people to start similar projects consistently. A template is the starting point for a new project; it isn’t the finished automation itself. docs.uipath.com
What is a UiPath Library?
A Library contains workflows or components that can be reused in other automation projects. When published and installed as a dependency, its reusable components can appear in Studio as activities.
Example: Create a reusable “Read Excel and validate rows” component. Add it to several processes instead of rebuilding the same logic in each one.
Choose Library when you want to share a particular capability across multiple projects. docs.uipath.com
Process vs Template vs Library
| Project type | Main purpose | Example |
|---|---|---|
| Process | Run a specific automation | Process invoices for one business |
| Template | Start new projects from a shared structure | Standard invoice automation setup |
| Library | Reuse components inside different projects | Shared Excel validation activity |
Which one should you choose?
Ask yourself what you want to reuse:
- Need to run a business task? Create a Process.
- Need to reuse a whole project setup? Create a Template.
- Need to reuse specific workflows or activities across projects? Create a Library.
Final takeaway
Think of it this way: a Process does the work, a Template helps you start a project, and a Library gives you reusable building blocks.
Remember: Process = run it. Template = start from it. Library = reuse parts of it.
