Forem: Ivan Muñoz

Deploying an HTML‑to‑PDF API on Vercel with Puppeteer

Ivan Muñoz — Tue, 12 Aug 2025 12:29:19 +0000

Original article https://buglesstack.com/blog/deploying-an-html-to-pdf-api-on-vercel-with-puppeteer/

In this article, we will explore how to create an HTML-to-PDF API on Vercel using Puppeteer.

You can find the complete code in the GitHub repository.

Demo

https://html-to-pdf-on-vercel.vercel.app/

Step 1: Project Setup

npx create-next-app@latest html-to-pdf-on-vercel --typescript --tailwind --app

Now, install the packages puppeteer-core @sparticuz/chromium for running Puppeteer in Vercel and puppeteer for local development:

npm install puppeteer-core @sparticuz/chromium
npm install -D puppeteer

Step 2: Setup the HTML to PDF api route

Create a new file at app/api/pdf/route.ts:

import { NextRequest, NextResponse } from "next/server";
import puppeteer from 'puppeteer-core';
import chromium from '@sparticuz/chromium';

export async function GET(request: NextRequest) {
  const { searchParams } = new URL(request.url);
  const htmlParam = searchParams.get("html");
  if (!htmlParam) {
    return new NextResponse("Please provide the HTML.", { status: 400 });
  }

  let browser;

  try {
    const isVercel = !!process.env.VERCEL_ENV;

    const pptr = isVercel ? puppeteer : (await import("puppeteer")) as unknown as typeof puppeteer;

    browser = await pptr.launch(isVercel ? {
      args: chromium.args,
      executablePath: await chromium.executablePath(),
      headless: true
    } : { 
      headless: true, 
      args: puppeteer.defaultArgs()
    });

    const page = await browser.newPage();
    await page.setContent(htmlParam, { waitUntil: 'load' });

    const pdf = await page.pdf({ 
        path: undefined,
        printBackground: true
    });
    return new NextResponse(Buffer.from(pdf), {
      headers: {
        "Content-Type": "application/pdf",
        "Content-Disposition": 'inline; filename="page-output.pdf"',
      },
    });
  } catch (error) {
    console.error(error);
    return new NextResponse(
      "An error occurred while generating the PDF.",
      { status: 500 }
    );
  } finally {
    if (browser) {
      await browser.close();
    }
  }
}

This route handles and HTML as a url query param and add it to the page with page.setContent() to then generate the PDF.

Step 3: Add a frontend to call the API

To interact with our API, let's create a simple frontend. Replace the content of app/page.tsx:

"use client";

import { useState } from "react";

const defaultHtml = `<p style="text-align:center">
  Hello World! 
  <br />
  <b>
    This PDF was created using 
    <br />
    <a href="https://github.com/ivanalemunioz/html-to-pdf-on-vercel">
      https://github.com/ivanalemunioz/html-to-pdf-on-vercel
    </a>
  </b>
</p>`;

export default function HomePage() {
  const [html, setHtml] = useState(defaultHtml);
  const [loading, setLoading] = useState(false);
  const [error, setError] = useState<string | null>(null);

  const createPDF = async () => {
    if (!html) {
      setError("Please enter a valid HTML.");
      return;
    }

    setLoading(true);
    setError(null);

    try {
      const response = await fetch(
        `/api/pdf?html=${encodeURIComponent(html)}`
      );
      if (!response.ok) {
        throw new Error("Failed to create PDF.");
      }
      const blob = await response.blob();
      const objectUrl = URL.createObjectURL(blob);
      const link = document.createElement('a');
      link.href = objectUrl;
      link.download = 'output.pdf'; // Desired filename
      document.body.appendChild(link); // Temporarily add to the DOM
      link.click(); // Programmatically click the link to trigger download
      document.body.removeChild(link); // Remove the link
      URL.revokeObjectURL(objectUrl); // Release the object URL
    } catch (err) {
      setError(
        err instanceof Error ? err.message : "An unknown error occurred."
      );
    } finally {
      setLoading(false);
    }
  };

  return (
    <main className="flex min-h-screen flex-col items-center justify-center p-24 bg-gray-50">
      <div className="w-full max-w-2xl text-center">
        <h1 className="text-4xl font-bold mb-4 text-gray-800">
          HTML to PDF on Vercel using Puppeteer
        </h1>
        <p className="text-lg text-gray-600 mb-8">
          Enter the HTML below to generate a PDF using Puppeteer running in
          a Vercel Function.
        </p>
        <div className="flex gap-2 flex-col">
          <textarea
            value={html}
            rows={13}
            onChange={(e) => setHtml(e.target.value)}
            placeholder="https://vercel.com"
            className="flex-grow p-3 border border-gray-300 rounded-lg focus:ring-2 focus:ring-blue-500 text-black focus:outline-none font-mono"
          />
          <button
            onClick={createPDF}
            disabled={loading}
            className="px-6 py-3 bg-blue-600 text-white font-semibold rounded-lg hover:bg-blue-700 disabled:bg-gray-400 transition-colors"
          >
            {loading ? "Creating PDF..." : "Create PDF"}
          </button>
        </div>
        {error && <p className="text-red-500 mt-4">{error}</p>}
      </div>
    </main>
  );
}

Step 4: Vercel Configuration

To ensure Puppeteer runs correctly when deployed, you need to configure Next.js.

Update your next.config.ts file.

import type { NextConfig } from "next";

const nextConfig: NextConfig = {
  /* config options here */
  // The `serverExternalPackages` option allows you to opt-out of bundling dependencies in your Server Components.
  serverExternalPackages: ["@sparticuz/chromium", "puppeteer-core"],
};

export default nextConfig;

Step 4: Try it

Run the development server:

npm run dev

Open http://localhost:3000 with your browser to try it.

Step 5: Deploy it to Vercel

How I finally stopped suffering from browser automation crashes

Ivan Muñoz — Mon, 11 Aug 2025 12:45:03 +0000

Let’s be real: browser automations crash. They crash often. And they crash when you least expect it—usually at 2 AM when you’re feeling smug about how “stable” your code is.

I’ve been building automations since 2016. My journey:

2016: Started with Electron. Yeah, I know—it’s like using a bus to deliver a pizza. But it ran on my machine, so it worked.
2018: Moved to PhantomJS. It’s dead now.
2021: Finally found Puppeteer. Thank the dev gods it was still alive when I joined.

Every single tool had one thing in common:
They all broke.
And when they did, I had the same headache—finding out what was going on inside the browser at the exact moment of the crash.

Sentry could tell me where my code broke. But if I was waiting for #query to appear and it never did, I didn’t just want a stack trace—I wanted to see what was there instead.

The Old Way (a.k.a. The Painful Way)

Here’s my old crash-debug workflow:

On crash, take a screenshot and HTML dump.
Save them to S3.
Save the URLs in my DB.
Wait for a Sentry email.
Go to the DB, find the row, click the links, download the files, open them… repeat until I lose the will to live.

This wasn’t a problem for small projects. But once my automations started getting real traffic, crashes multiplied like rabbits. Suddenly I was spending more time hunting crash data than actually fixing bugs.

So I did what any lazy developer does when a process is too slow and annoying…

The New Way (a.k.a. I Built My Own Tool)

Introducing: Buglesstack 🎺🐛

Instead of the clunky manual process, every crash now sends one complete report straight to Buglesstack with:

Error message
Error stack
Browser URL at the crash moment
Full-page screenshot
Full HTML snapshot
Any custom metadata I want

Now when something breaks, I just open Buglesstack, see everything in one place, and fix it right away.

The funny thing? Crashes that used to sit on my to-do list for days now get fixed the same day. Not because they’re easier—because I’m no longer wasting time jumping between my DB, S3, and local files like a circus act.

Why I Made It Public

Once I saw how much faster this made my life, I thought, “Other devs probably hate their crash workflow too.”

So I opened Buglesstack as Open Source, you can follow the instructions to install it or use the cloud version.

Upcoming stuff: email notifications, crash archiving, filtering, grouping—you name it. I’m my own biggest user, so I’m constantly adding the things I wish it had yesterday.

If you try it and have ideas, email me at ivan@buglesstack.com. I’m all ears.

Bonus: Happy Customers

Thanks to Buglesstack, I can now instantly answer my customers when their automation fails.

Example: one crash report showed a “503 Service Unavailable” page. I just screenshotted the report preview and said:

Hi, it’s not us—the site you’re automating is down.

That’s it. No digging. No guessing.
The customer was happy. I was happy. Everyone wins.

If your browser automations crash (and they will), don’t make debugging a treasure hunt. Give Buglesstack a spin.

How to create an API to generate PDFs using Puppeteer with auto-deploy to AWS Lambda

Ivan Muñoz — Mon, 21 Jul 2025 11:09:42 +0000

Original Article: How to create an API to generate PDFs using Puppeteer with auto-deploy to AWS Lambda

In this article, we will explore how to set up an API to generate PDFs using Puppeteer, with auto-deploy to AWS Lambda using GitHub Actions.

It includes a repo that serves as a base template for deploying a Puppeteer project to AWS Lambda using GitHub Actions. The repo is designed to convert your Puppeteer project into an API that can be invoked via HTTP requests, allowing you to run Puppeteer scripts in a serverless environment.

You can find the complete code in the GitHub repository.

Development
1. Cloning the repository
2. Installing dependencies
3. Creating the .env file
4. Running the development server
5. Testing the API
Deployment
1. Creating the Lambda function
2. Creating the S3 bucket
3. Creating an IAM user and access keys
4. Configuring your lambda function
5. Configuring the GitHub Actions workflow
6. Testing the deployment
Troubleshooting
Conclusion
Additional Resources

Development

1. Cloning the repository

Clone the repository to your local machine:

git clone https://github.com/ivanalemunioz/puppeteer-pdf-lambda-auto-deploy.git
cd puppeteer-pdf-lambda-auto-deploy

2. Installing dependencies

Install the required dependencies using npm:

npm install

3. Creating the .env file

Create a .env file in the root of the project based on the .env.example file and fill in the required values.

4. Running the development server

Run the development server:

npm run dev

This command will start the server on http://localhost:5124 and will watch for changes in the code.

5. Testing the API

Test the API by sending a POST request to http://localhost:5124/v1/pdf/html using a tool like Postman or curl. You should see the Puppeteer script running and returning a response.

You can set the "options" parameter using the options from https://pptr.dev/api/puppeteer.pdfoptions

curl --location 'http://localhost:5124/v1/pdf/html' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_GENERATED_AUTH_TOKEN' \
--data '{
    "html": "<p style='\''text-align:center'\''>Hello World! <b>This PDF was created using <a href='\''https://github.com/ivanalemunioz/puppeteer-pdf-lambda-auto-deploy'\''>https://github.com/ivanalemunioz/puppeteer-pdf-lambda-auto-deploy</a></b></p>",
    "file_name": "Test PDF file",
    "options" : {}
}'

Deployment

You can jump to step 4 if you already have a Lambda function, S3 bucket and IAM role set up.

1. Creating the Lambda function

Go to the AWS Lambda console.
Click on "Create function".
Choose "Author from scratch".
Enter a name for your function, e.g., puppeteer-pdf-lambda-auto-deploy.
Select the runtime as Node.js 22.x.
Select the architecture as x86_64. It will not work with arm64 architecture.
Under "Additional configurations", enable "Function URL" to allow HTTP access to your Lambda function.
- "Auth type" select NONE.
- "Invoke mode" select "BUFFERED (default)".
Click on "Create function".

2. Creating the S3 bucket

Go to the S3 console.
Click on "Create bucket".
As bucket type select "General purpose".
Enter a unique name for your bucket, e.g., puppeteer-pdf-lambda-auto-deploy-bucket.
Let the rest of the settings as default.
Click on "Create bucket".

3. Creating an IAM user and access keys

Go to the IAM console.
Click on "Users" in the left sidebar.
Click on "Create user".
Enter a username, e.g., puppeteer-pdf-lambda-auto-deploy-user.
Click on "Next".
Click on "Attach policies directly" and select the following policies:
- AWSLambda_FullAccess
- AmazonS3FullAccess
Click on "Create user".
Click on the user you just created.
Under the "Security credentials" tab, click on "Create access key".
As Use case select "Other"
Click on "Next".
Click on "Create access key".
Copy the Access key ID and Secret access key and store them securely.

4. Configuring your lambda function

Go to the AWS Lambda console.
Click on the function you created earlier.
Under the "Configuration" tab, click on "Environment variables".
Click in "Edit" and add the BUGLESSTACK_ACCESS_TOKEN and BROWSER_AUTOMATIONS_ACCESS_TOKEN variables. You can get more info about how to generate these tokens in the .env.example file.
- Optionally, if you want to store the PDFs in a s3 bucket add S3_BUCKET_FOR_STORAGE variable and S3_ACCESS_KEY_ID, S3_SECRET_ACCESS_KEY and S3_REGION
Under the "Configuration" tab, click on "General configuration" and "Edit".
Increase the timeout to 2 minutes and memory to 1024MB (recommended) and click on "Save".

5. Configuring the GitHub Actions workflow

Go to your GitHub repository.
Click on "Settings" in the top menu.
In the left sidebar, click on "Secrets and variables" and then "Actions".
Add the following secrets:
- AWS_ACCESS_KEY_ID: Your AWS access key ID generated in step 3.
- AWS_SECRET_ACCESS_KEY: Your AWS secret access key generated in step 3.
- AWS_REGION: The AWS region where your Lambda function is deployed (e.g., us-east-1).
In the same section, click on "Variables" and add the following variables:
- S3_BUCKET: The name of the S3 bucket where the Lambda function package will be uploaded.
- S3_KEY: The key (path) in the S3 bucket where the Lambda function package will be stored (e.g., lambda/puppeteer.zip).
- S3_LAYER_BUCKET: The name of the S3 bucket where the Lambda layer package will be uploaded.
- S3_LAYER_KEY: The key (path) in the S3 bucket where the Lambda layer package will be stored (e.g., layers/puppeteer.zip).
- LAYER_NAME: The name of the Lambda layer to be created or updated (e.g., puppeteer-pdf-lambda-auto-deploy-layer).
- LAMBDA_FUNCTION_NAME: The name of the Lambda function to be updated (e.g., puppeteer-pdf-lambda-auto-deploy).
In "Settings > Actions > General", ensure that "Allow all actions and reusable workflows" is selected under "Actions permissions".

6. Testing the deployment

Push your changes to the main branch of your GitHub repository.
The GitHub Actions workflow will automatically build and deploy your Puppeteer project to AWS Lambda.

Once the workflow is complete, you can test the API by sending a POST request to https://YOUR_LAMBDA_URL/v1/pdf/html (you can get your Lambda URL in the Lambda details) using a tool like Postman or curl. You should see the Puppeteer script running and returning a response.

You can set the "options" parameter using the options from https://pptr.dev/api/puppeteer.pdfoptions

curl --location 'https://YOUR_LAMBDA_URL/v1/pdf/html' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_GENERATED_AUTH_TOKEN' \
--data '{
    "html": "<p style='\''text-align:center'\''>Hello World! <b>This PDF was created using <a href='\''https://github.com/ivanalemunioz/puppeteer-pdf-lambda-auto-deploy'\''>https://github.com/ivanalemunioz/puppeteer-pdf-lambda-auto-deploy</a></b></p>",
    "file_name": "Test PDF file",
    "options" : {}
}'

Troubleshooting

If you encounter issues with Puppeteer not launching or crashing, ensure that the Lambda function has sufficient memory allocated (at least 1024 MB is recommended).
Configure the Lambda function timeout to a reasonable value (e.g., 30 seconds) to allow Puppeteer enough time to execute.
Ensure your Lambda architecture is set to x86_64, it will not work with arm64 architecture.
Ensure your Lambda and S3 bucket are in the same region.
Check the permissions of the IAM user to ensure it has access to S3 and Lambda.
Check the AWS Lambda logs in CloudWatch Logs for any errors or issues during execution.
If you encounter issues with the Github Actions workflow, check the workflow logs for any errors or issues during the build and deployment process.

Conclusion

In this guide, you learned how to set up an API to create PDFs with Puppeteer, and a CI/CD pipeline using GitHub Actions and AWS Lambda. By following these steps, you can automate the deployment of your Puppeteer scripts to AWS Lambda, making it easier to run headless browser tasks in the cloud. This setup not only streamlines your development workflow but also leverages the scalability and reliability of AWS Lambda for running your Puppeteer scripts.

You can find the complete code in the GitHub repository.

You can also explore the Buglesstack integration for error tracking and monitoring, which is included in the project.

You can also check the GitHub Actions workflow file.

Additional Resources

How to auto-deploy Puppeteer in AWS Lambda using Github actions

Ivan Muñoz — Sat, 19 Jul 2025 12:12:20 +0000

Original Article: How to auto-deploy Puppeteer in AWS Lambda using Github actions

In this article, we will explore how to set up a Puppeteer project that can be automatically deployed to AWS Lambda using GitHub Actions.

You can find the complete code in the GitHub repository.

Development
1. Cloning the repository
2. Installing dependencies
3. Creating the .env file
4. Running the development server
5. Testing the API
Deployment
1. Creating the Lambda function
2. Creating the S3 bucket
3. Creating an IAM user and access keys
4. Configuring your lambda function
5. Configuring the GitHub Actions workflow
6. Testing the deployment
Troubleshooting
Conclusion
Additional Resources

Development

1. Cloning the repository

Clone the repository to your local machine:

git clone https://github.com/ivanalemunioz/puppeteer-lambda-auto-deploy.git
cd puppeteer-lambda-auto-deploy

2. Installing dependencies

Install the required dependencies using npm:

npm install

3. Creating the .env file

Create a .env file in the root of the project based on the .env.example file and fill in the required values.

4. Running the development server

Run the development server:

npm run dev

This command will start the server on http://localhost:5123 and will watch for changes in the code.

5. Testing the API

You can test the API by sending a POST request to http://localhost:5123/v1/run using a tool like Postman or curl. You should see the Puppeteer script running and returning a response.

curl --location 'http://localhost:5123/v1/run' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_GENERATED_AUTH_TOKEN' \
--data '{
    "action": "scrape-pptr-docs",
    "params": {}
}'

Deployment

You can jump to step 4 if you already have a Lambda function, S3 bucket and IAM role set up.

1. Creating the Lambda function

Go to the AWS Lambda console.
Click on "Create function".
Choose "Author from scratch".
Enter a name for your function, e.g., puppeteer-lambda-auto-deploy.
Select the runtime as Node.js 22.x.
Select the architecture as x86_64. It will not work with arm64 architecture.
Under "Additional configurations", enable "Function URL" to allow HTTP access to your Lambda function.
- "Auth type" select NONE.
- "Invoke mode" select "BUFFERED (default)".
Click on "Create function".

2. Creating the S3 bucket

Go to the S3 console.
Click on "Create bucket".
As bucket type select "General purpose".
Enter a unique name for your bucket, e.g., puppeteer-lambda-auto-deploy-bucket.
Let the rest of the settings as default.
Click on "Create bucket".

3. Creating an IAM user and access keys

Go to the IAM console.
Click on "Users" in the left sidebar.
Click on "Create user".
Enter a username, e.g., puppeteer-lambda-auto-deploy-user.
Click on "Next".
Click on "Attach policies directly" and select the following policies:
- AWSLambda_FullAccess
- AmazonS3FullAccess
Click on "Create user".
Click on the user you just created.
Under the "Security credentials" tab, click on "Create access key".
As Use case select "Other"
Click on "Next".
Click on "Create access key".
Copy the Access key ID and Secret access key and store them securely.

4. Configuring your lambda function

Go to the AWS Lambda console.
Click on the function you created earlier.
Under the "Configuration" tab, click on "Environment variables".
Click in "Edit" and add the BUGLESSTACK_ACCESS_TOKEN and BROWSER_AUTOMATIONS_ACCESS_TOKEN variables. You can get more info about how to generate these tokens in the .env.example file.
Under the "Configuration" tab, click on "General configuration" and "Edit".
Increase the timeout to 2 minutes and memory to 1024MB (recommended) and click on "Save".

5. Configuring the GitHub Actions workflow

Go to your GitHub repository.
Click on "Settings" in the top menu.
In the left sidebar, click on "Secrets and variables" and then "Actions".
Add the following secrets:
- AWS_ACCESS_KEY_ID: Your AWS access key ID generated in step 3.
- AWS_SECRET_ACCESS_KEY: Your AWS secret access key generated in step 3.
- AWS_REGION: The AWS region where your Lambda function is deployed (e.g., us-east-1).
In the same section, click on "Variables" and add the following variables:
- S3_BUCKET: The name of the S3 bucket where the Lambda function package will be uploaded.
- S3_KEY: The key (path) in the S3 bucket where the Lambda function package will be stored (e.g., lambda/puppeteer.zip).
- S3_LAYER_BUCKET: The name of the S3 bucket where the Lambda layer package will be uploaded.
- S3_LAYER_KEY: The key (path) in the S3 bucket where the Lambda layer package will be stored (e.g., layers/puppeteer.zip).
- LAYER_NAME: The name of the Lambda layer to be created or updated (e.g., puppeteer-lambda-auto-deploy-layer).
- LAMBDA_FUNCTION_NAME: The name of the Lambda function to be updated (e.g., puppeteer-lambda-auto-deploy).
In "Settings > Actions > General", ensure that "Allow all actions and reusable workflows" is selected under "Actions permissions".

6. Testing the deployment

Push your changes to the main branch of your GitHub repository.
The GitHub Actions workflow will automatically build and deploy your Puppeteer project to AWS Lambda.
Once the workflow is complete, you can test the API by sending a POST request to https://YOUR_LAMBDA_URL/v1/run (you can get your Lambda URL in the Lambda details) using a tool like Postman or curl. You should see the Puppeteer script running and returning a response.
```
curl --location 'https://YOUR_LAMBDA_URL/v1/run' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_GENERATED_AUTH_TOKEN' \
--data '{
    "action": "scrape-pptr-docs",
    "params": {}
}'
```

Troubleshooting

If you encounter issues with Puppeteer not launching or crashing, ensure that the Lambda function has sufficient memory allocated (at least 1024 MB is recommended).
Configure the Lambda function timeout to a reasonable value (e.g., 30 seconds) to allow Puppeteer enough time to execute.
Ensure your Lambda architecture is set to x86_64, it will not work with arm64 architecture.
Ensure your Lambda and S3 bucket are in the same region.
Check the permissions of the IAM user to ensure it has access to S3 and Lambda.
Check the AWS Lambda logs in CloudWatch Logs for any errors or issues during execution.
If you encounter issues with the Github Actions workflow, check the workflow logs for any errors or issues during the build and deployment process.

Conclusion

In this guide, you learned how to set up a CI/CD pipeline for your Puppeteer project using GitHub Actions and AWS Lambda. By following these steps, you can automate the deployment of your Puppeteer scripts to AWS Lambda, making it easier to run headless browser tasks in the cloud. This setup not only streamlines your development workflow but also leverages the scalability and reliability of AWS Lambda for running your Puppeteer scripts.

You can find the complete code in the GitHub repository.

You can also explore the Buglesstack integration for error tracking and monitoring, which is included in the project.

You can also check the GitHub Actions workflow file.

Forem: Ivan Muñoz

Deploying an HTML‑to‑PDF API on Vercel with Puppeteer

Demo

Step 1: Project Setup

Step 2: Setup the HTML to PDF api route

Step 3: Add a frontend to call the API

Step 4: Vercel Configuration

Step 4: Try it

Step 5: Deploy it to Vercel

How I finally stopped suffering from browser automation crashes

The Old Way (a.k.a. The Painful Way)

The New Way (a.k.a. I Built My Own Tool)

Why I Made It Public

Bonus: Happy Customers

How to create an API to generate PDFs using Puppeteer with auto-deploy to AWS Lambda

Table of Contents

Development

1. Cloning the repository

2. Installing dependencies

3. Creating the .env file

4. Running the development server

5. Testing the API

Deployment

1. Creating the Lambda function

2. Creating the S3 bucket

3. Creating an IAM user and access keys

4. Configuring your lambda function

5. Configuring the GitHub Actions workflow

6. Testing the deployment

Troubleshooting

Conclusion

Additional Resources

How to auto-deploy Puppeteer in AWS Lambda using Github actions

Table of Contents

Development

1. Cloning the repository

2. Installing dependencies

3. Creating the .env file

4. Running the development server

5. Testing the API

Deployment

1. Creating the Lambda function

2. Creating the S3 bucket

3. Creating an IAM user and access keys

4. Configuring your lambda function

5. Configuring the GitHub Actions workflow

6. Testing the deployment

Troubleshooting

Conclusion

Additional Resources