> ## Documentation Index
> Fetch the complete documentation index at: https://www.nexrender.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Deleting Templates

> How to delete templates from Nexrender Cloud and what happens after.

Nexrender Cloud allows you to delete templates that are no longer needed. This is useful for:

* Removing test or temporary assets
* Cleaning up deprecated campaign templates
* Managing storage usage in your account

## When Should You Delete a Template?

You might want to delete a template when:

* It has been replaced by a newer version
* It was used for testing and is no longer relevant
* You’re cleaning up automation clutter in your account

> Deleting a template **does not affect** existing jobs that already used it. Those jobs remain in the system and their output remains accessible.

## What Happens After Deletion?

| Component         | Status                                             |
| ----------------- | -------------------------------------------------- |
| Template metadata | Permanently deleted from Nexrender Cloud           |
| Uploaded file     | Removed from storage (Cloudflare R2 or equivalent) |
| Associated jobs   | Remain intact — no data loss                       |
| Rendering         | New jobs using this template will fail with 404    |

If you attempt to reference a deleted template in a job request, you’ll receive a `404 Template Not Found`.

## Edge Cases & Notes

* You **cannot delete** a template while it's actively rendering.
* If a template is in `awaiting_upload`, you can delete it immediately.
* Deletion is **immediate and irreversible** — no soft-delete or recovery options.
* You can safely delete templates that had webhook or font dependencies — those are not linked permanently.

## Suggested Practice

To keep things clean:

* Delete unused templates after testing flows
* Use versioned `displayName`s so you know what’s safe to remove
* Add deletion as part of your CI teardown if you're creating templates dynamically.

## API Reference


## OpenAPI

````yaml DELETE /templates/{id}
openapi: 3.0.4
info:
  title: Nexrender API
  version: '2.0'
  description: >
    REST API for the Nexrender cloud rendering platform, enabling programmatic
    control over After Effects template processing, job management, and asset
    handling.


    Features include:


    - Template upload and management (AEP, MOGRT, ZIP files)

    - Job creation and status monitoring with real-time progress

    - Job nesting for multi-composition renders (parent/child jobs)

    - Job stitching to combine multiple videos into one

    - Batch job creation for submitting up to 1000 jobs at once

    - Font library management for typography consistency

    - Secret management for secure API key storage

    - Webhook notifications for job lifecycle events

    - Asset injection for dynamic content replacement


    Authentication is required for all endpoints using Bearer token
    authorization.
servers:
  - url: https://api.nexrender.com/api/v2
    description: Production API server
security:
  - apiToken: []
paths:
  /templates/{id}:
    delete:
      tags:
        - Template Management
      summary: Delete template
      description: >-
        Permanently remove a template and all associated data (cannot be undone,
        affects existing jobs)
      operationId: deleteTemplate
      parameters:
        - in: path
          name: id
          required: true
          description: Unique template identifier to delete
          schema:
            type: string
      responses:
        '204':
          description: Template successfully deleted
        '401':
          description: Unauthorized - invalid or missing API token
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: Template not found - the specified template ID does not exist
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '409':
          description: >-
            Conflict - template is currently in use by active jobs and cannot be
            deleted
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    ErrorResponse:
      type: object
      description: Standard error response format
      properties:
        error:
          type: string
          description: Human-readable error message explaining what went wrong
      required:
        - error
  securitySchemes:
    apiToken:
      type: http
      scheme: bearer
      description: >
        Bearer token authentication using API tokens for team-based access
        control.


        You can generate your own API token at:
        https://app.nexrender.com/settings/api-tokens

````