edge.html

---
layout: default
title: PyTorch Edge
body-class: announcement
background-class: announcement-background
permalink: /edge
---

<div class="container">
  <div class="row hero-content">
    <div class="col-md-8">
      <h1 class="small">PyTorch Edge</h1>
      <p class="lead pt-3">Build innovative and privacy-aware AI experiences for edge devices</p>
    </div>
    <div class="col-md-2 d-none d-lg-block">
      <img width=100 src="/assets/images/pytorch-edge-arrows.svg">
    </div>
  </div>
</div>

<div class="container-fluid light-background-section">
  <div class="container">
    <div class="row">
      <div class="col-md-10">
        <h2 class="mt-5 mb-2">PyTorch Edge</h2>
        <p>The AI landscape is quickly evolving, with AI models being deployed beyond server to edge devices such as mobile phones, wearables, AR/VR/MR and embedded devices. PyTorch Edge extends PyTorch's research-to-production stack to these edge devices and paves the way for building innovative, privacy-aware experiences with superior productivity, portability, and performance, optimized for these diverse hardware platforms. </p>
        <h2 class="mt-5 mb-2">PyTorch on Edge - From PyTorch Mobile to ExecuTorch</h2>
        <p>In 2019, we announced <a href="/mobile/home/">PyTorch Mobile</a> powered by <a href="https://pytorch.org/docs/stable/jit.html">TorchScript</a> to address the ever-growing need for edge devices to execute AI models. To advance our PyTorch Edge offerings even further, we developed <a href="/executorch-overview">ExecuTorch</a>. ExecuTorch facilitates PyTorch inference on edge devices while supporting portability across hardware platforms with lower runtime and framework tax. ExecuTorch was developed collaboratively between industry leaders including Meta, Arm, Apple, and Qualcomm. </p>
        <p>PyTorch Mobile allowed users to stay in the PyTorch ecosystem from training to model deployment. However, the lack of consistent PyTorch semantics used across these and the focus on TorchScript inhibited the developer experience and slowed down research to production. PyTorch Mobile also didn’t provide well-defined entry points for third-party integration and optimizations, which we’ve addressed with ExecuTorch. </p>
        <p>We’ve renewed our commitment to on-device AI with <a href="/executorch-overview">ExecuTorch</a>. This extends our ecosystem in a much more “in the spirit of PyTorch” way, with productivity, hackability, and extensibility as critical components. We look forward to supporting edge and embedded applications with low latency, strong privacy, and innovation on the edge. </p>
    </div>
  </div>
</div>

<div class="container-fluid light-background-section mb-5">
  <div class="container">
    <div class="row content pb-0">
      <div class="col-md-10 text-center">
        <h2>Learn more about PyTorch Edge</h2>
      </div>
    </div>
    <div class="row content">
      <div class="col-md-4 text-center">
        <p class="lead">New on-device inference</p>
        <a href="/executorch-overview" class="btn btn-lg mb-4 with-right-arrow">
          ExecuTorch
        </a>
      </div>
      <div class="col-md-4 text-center">
        <p class="lead">Legacy PyTorch Mobile runtime</p>
        <a href="/mobile/home" class="btn btn-lg with-right-arrow">
          PyTorch Mobile
        </a>
      </div>
    </div>
  </div>
</div>