Tasks in Payload's job queue can now run in parallel rather than sequentially. This means multi-step background operations complete significantly faster, especially for workflows that process independent chunks of work — like generating multiple image sizes, sending batch notifications, or running scheduled imports.

1// payload.config.ts
2export default buildConfig({
jobs: {
  tasks: [
    {
      slug: "resizeImage",
      inputSchema: [{ name: "mediaId", type: "text", required: true }],
      handler: async ({ input }) => {
        // resize logic
      },
    },
    {
      slug: "generateThumbnail",
      inputSchema: [{ name: "mediaId", type: "text", required: true }],
      handler: async ({ input }) => {
        // thumbnail logic
      },
    },
  ],
  workflows: [
    {
      slug: "processUpload",
      inputSchema: [{ name: "mediaId", type: "text", required: true }],
      handler: async ({ job, tasks }) => {
        // Both tasks now run in parallel
        await Promise.all([
          tasks.resizeImage({ input: { mediaId: job.input.mediaId } }),
          tasks.generateThumbnail({ input: { mediaId: job.input.mediaId } }),
        ]);
      },
    },
  ],
},
34});

Conditional blocks in Lexical — v3.57

Blocks in the Lexical editor can now be shown or hidden based on the values of other fields. This gives content editors a cleaner, context-aware editing experience and lets developers build content structures that adapt without cluttering the UI with irrelevant options.

1// collections/Posts.ts
2export const Posts: CollectionConfig = {
slug: "posts",
fields: [
  {
    name: "type",
    type: "select",
    options: ["standard", "premium"],
  },
  {
    name: "content",
    type: "blocks",
    blocks: [StandardBlock, PremiumBlock],
    admin: {
      condition: (data, siblingData) => Boolean(siblingData?.type),
    },
  },
  {
    name: "premiumContent",
    type: "blocks",
    blocks: [PremiumBlock],
    admin: {
      condition: (data, siblingData) => siblingData?.type === "premium",
    },
  },
],
27};

Drag-and-drop / copy-paste into Lexical — v3.57

You can now drag image files or other media directly from your desktop into the Lexical editor, or paste them straight from your clipboard. Previously this required uploading through the media browser first — now it works the way editors expect.

Slug field — v3.59

Payload now ships a dedicated slug field type. It generates a URL-safe slug from another field (typically the title), with built-in controls to lock or unlock it for manual editing. No more writing custom beforeChange hooks to manage slugs.

1import { slugField } from "payload/fields";
2
3export const Posts: CollectionConfig = {
slug: "posts",
fields: [
  {
    name: "title",
    type: "text",
    required: true,
  },
  slugField({
    useAsSlug: "title",
    required: true,
  }),
],
16};

See what others are building with Payload.

"Payload has transformed the way our clients manage content. It's an indispensable tool for any modern agency."

Get the resources you need to start building today

Microsoft chose Payload to tell the world about AI.

New in Payload: Jobs, Content Modeling, and Lexical Improvements

From parallel background jobs to a dedicated slug field and a smarter rich text editor, v3.50 through v3.65 brought some of the most requested features to Payload's core. Here's what landed.

Parallel job queue tasks — v3.54

Conditional blocks in Lexical — v3.57

Drag-and-drop / copy-paste into Lexical — v3.57

Slug field — v3.59

Related Posts

New in Payload: Trash Support, Job Scheduling, and DX Enhancements