The outcome

Get into the official LM Studio experience with the right account and a setup you understand.

LM Studio is a desktop and headless runtime for downloading, evaluating, and serving local language models. Running supported open models locally, comparing model configurations, chatting with private local data, and providing local application APIs. This guide narrows that broad capability into one repeatable outcome, with checkpoints that keep the source material and your judgment in the loop.

Before you begin

Set the boundary before the tool starts.

Choose one real task, identify who will use the result, and decide what evidence or test will make the result acceptable. Gather only the source material needed for that task. If the work contains confidential, personal, regulated, or client-owned information, confirm that the platform and account are approved before sharing it.

Troiana principle

AI should make the work easier to inspect. If the workflow removes the source, the owner, or the review step, redesign the workflow.

Step by step

A workflow you can repeat.

  1. 01

    Start at https://lmstudio.ai/ and confirm the domain before entering account or payment information.

  2. 02

    For desktop use, follow the official download link. Current availability: Desktop builds are available for supported macOS, Windows, and Linux systems; a headless runtime is also documented..

  3. 03

    A supported processor and operating system, sufficient RAM and storage for selected models, and preferably compatible GPU memory for larger workloads.

  4. 04

    Sign in with the account you intend to keep using, then review plan, data, notification, and permission settings.

  5. 05

    Run one low-risk test task before connecting sensitive files, repositories, or workspace data.

Working standard

What good use looks like.

  • Use official download pages.
  • Review permissions during setup.
  • Keep installers and applications updated.

Local inference does not make model output trustworthy, and the API server has no authentication by default. Review model licenses and cards, keep the server on localhost unless necessary, require a token before network exposure, and tightly control CORS and MCP access.

Official references

Check the current product documentation.

Features, plan limits, availability, and data controls change. These official pages are the starting points used for this collection.