Using Media with Cloudinary

Manage Cloudinary media assets in TinaCMS.


yarn add next-tinacms-cloudinary @tinacms/auth

Connect with Cloudinary

You need to provide your Cloudinary credentials to connect to your media library. Do register on Cloudinary if you don't have an account yet, your account details are displayed on the Cloudinary dashboard.

next-tinacms-cloudinary uses environment variables within the context of a Next.js site to properly access your Cloudinary account.

Add the following variables to an .env file.

CLOUDINARY_API_SECRET=<Your Cloudinary API secret>

Register the Media Store

Now, you can register the Cloudinary Media store with the instance of Tina in your app by passing the TinaCloudCloudinaryMediaStore to the TinaCMS instance via its mediaStore prop.

This is also where we can update our mediaOptions on the cms object.

import { TinaEditProvider } from "tinacms/dist/edit-state";

const TinaCMS = dynamic(() => import("tinacms"), { ssr: false });

const App = ({ Component, pageProps }) => {
  return (
            // ...
            mediaStore={async () => {
              // Load media store dynamically so it only loads in edit mode
              const pack = await import("next-tinacms-cloudinary");
              return pack.TinaCloudCloudinaryMediaStore;

Set up API routes

Set up a new API route in the pages directory of your Next.js app, e.g. pages/api/cloudinary. Then add a new catch all API route for media.

Call createMediaHandler to set up routes and connect your instance of the Media Store to your Cloudinary account.

Import isAuthorized from "@tinacms/auth".

The authorized key will make it so only authorized users within Tina Cloud can upload and make media edits.


import {
} from 'next-tinacms-cloudinary/dist/handlers'

import { isAuthorized } from '@tinacms/auth'

export const config = mediaHandlerConfig

export default createMediaHandler({
  cloud_name: process.env.NEXT_PUBLIC_CLOUDINARY_CLOUD_NAME,
  api_key: process.env.NEXT_PUBLIC_CLOUDINARY_API_KEY,
  api_secret: process.env.CLOUDINARY_API_SECRET,
  authorized: async (req, _res) => {
    try {
      if (process.env.NEXT_PUBLIC_USE_LOCAL_CLIENT) {
        return true

      const user = await isAuthorized(req)

      return user && user.verified
    } catch (e) {
      return false

Update Schema

Now that the media store is registered and the API route for media set up, let's add an image to your schema.

In your .tina/schema.ts add a new field for the image, e.g:

  name: 'hero',
  type: 'image',
  label: 'Hero Image',

Now, when editing your site, the image field will allow you to connect to your Cloudinary account via the Media Store to manage your media assets.