Bolt.new AI and Backblaze B2 integration: Step-by-Step Guide 2025

The integration works by writing normal Backblaze B2 API or SDK calls inside your bolt.new project, and providing the required B2 credentials as environment variables. Bolt.new does not have any built‑in “B2 connector.” You integrate the same way you would in any Node.js full‑stack app: authenticate with B2, request an upload URL, upload files, download files, and manage buckets using Backblaze’s documented REST API. Inside bolt.new this works exactly the same — you just run the API calls in backend code and store B2 keys in environment variables.

 

What You Actually Do (the real, working integration path)

 

Backblaze B2 is a cloud object storage service. You talk to it using its official REST API or its official Node.js SDK. Bolt.new runs normal Node.js backend code, so integration is straightforward: install the SDK, add environment variables, write API calls.

The steps below are the correct real‑world recipe — nothing magic, nothing bolt‑specific.

• Create a Backblaze B2 application key + key ID.
• Put them into bolt.new Environment Variables (never hardcode secrets).
• Install Backblaze’s official Node.js SDK inside bolt.new.
• Write backend code that authenticates and uploads/downloads files.
• Expose routes or functions your front‑end can call.

 

Create B2 Credentials

 

Inside Backblaze’s dashboard:

• Go to App Keys.
• Create a key with the scope and bucket you want.
• Copy keyID and applicationKey.

Treat them like passwords.

 

Add Environment Variables in bolt.new

 

In your bolt.new workspace open the Environment panel and add:

• B2_KEY_ID = yourKeyID
• B2_APP_KEY = yourApplicationKey
• B2_BUCKET_ID = the bucket you want to use

These are now available in your backend code via process.env.

 

Install the Backblaze Node.js SDK

 

npm install backblaze-b2

 

Write Backend Code to Authenticate and Upload

 

This is real, working Backblaze B2 Node.js code you can paste into your bolt.new backend (for example in an API route like api/upload.js):

// api/upload.js
import B2 from "backblaze-b2";

export async function POST(request) {
  try {
    const b2 = new B2({
      applicationKeyId: process.env.B2_KEY_ID,
      applicationKey: process.env.B2_APP_KEY
    });

    await b2.authorize(); // required before any B2 calls

    const body = await request.formData();
    const file = body.get("file");

    const bucketId = process.env.B2_BUCKET_ID;

    // Step: get an upload URL
    const upload = await b2.getUploadUrl({ bucketId });

    // Step: upload file bytes
    const arrayBuffer = await file.arrayBuffer();
    const buffer = Buffer.from(arrayBuffer);

    const result = await b2.uploadFile({
      uploadUrl: upload.data.uploadUrl,
      uploadAuthToken: upload.data.authorizationToken,
      fileName: file.name,
      data: buffer
    });

    return new Response(
      JSON.stringify({ success: true, fileId: result.data.fileId }),
      { status: 200 }
    );

  } catch (err) {
    console.error(err);
    return new Response(JSON.stringify({ error: "Upload failed" }), { status: 500 });
  }
}

 

Front-End Example (bolt.new front-end talking to your API)

 

// Example in a React component inside bolt.new

async function uploadToB2(file) {
  const form = new FormData();
  form.append("file", file);

  const res = await fetch("/api/upload", {
    method: "POST",
    body: form
  });

  return res.json(); // contains fileId / metadata
}

 

Downloading Files from B2

 

For public buckets, you can simply serve the file URL:

• https://f000.backblazeb2.com/file/yourBucketName/yourFileName

For private buckets, generate an authorized download URL:

// Example backend route

const result = await b2.getDownloadAuthorization({
  bucketId: process.env.B2_BUCKET_ID,
  fileNamePrefix: "",
  validDurationInSeconds: 300 // 5 minutes signed URL
});

 

How This Works Inside bolt.new

 

bolt.new doesn’t have its own “integration layer.” You are running normal Node.js. So:

• You install dependencies.
• You write backend routes.
• You store secrets in environment variables.
• You call external APIs exactly like any other application.

This means the integration you build inside bolt.new is identical to what you'd deploy later to Vercel, AWS, or any other production environment.

 

Most Important Constraints to Remember

 

• B2 operations require authorization before every session.
• Uploads must use getUploadUrl first — you cannot upload directly to the API endpoint without this step.
• Never expose your B2 keys to the front‑end.
• Larger files may require streaming; the example above works for typical uploads.

 

This is the clean, real, correct way to integrate Bolt.new AI projects with Backblaze B2.