# Running Umbraco on Linux/macOS

With Umbraco CMS on .NET Core, Linux and macOS is natively supported with SQLite as the database.

In the below section, we describe how to get started with running Umbraco CMS on Linux or macOS.

## How to get started running Umbraco CMS on Linux or macOS

To get started with Umbraco CMS first have a look at the [requirements for running Umbraco CMS](https://docs.umbraco.com/umbraco-cms/fundamentals/requirements#local-development).

Once you've made sure you meet the requirements it is time to install the Umbraco Templates on your system.

To do this follow the [Install using .NET CLI](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/install-umbraco-with-templates#install-the-template) guide.

With the templates installed on your system, it is now possible to create Umbraco projects.

To create a project, there are two options:

* Continue creating projects using the .NET CLI.
* Create new projects using Visual Studio (only macOS).

To create new projects using Visual Studio, you can use the [Install using Visual Studio](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/install/visual-studio) guide.

Once you create a new project it will use SQLite by default on Linux/macOS.

If you prefer using SQL Server as your database, you can either install it locally or run it via [Docker](https://skrift.io/issues/umbraco-and-docker-part-1-getting-familiar-with-containers/).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.umbraco.com/umbraco-cms/fundamentals/setup/install/running-umbraco-on-linux-macos.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.