# Pinterest Video Downloader - No Audio (`alpha-scraper/pinterest-video-downloader-no-audio`) Actor

Pinterest Video Downloader - No Audio extracts public Pinterest video and image data from one or multiple pin URLs. Collect structured metadata, titles, descriptions, uploader details, engagement stats, thumbnails, media URLs, dimensions, duration, and resolution.

- **URL**: https://apify.com/alpha-scraper/pinterest-video-downloader-no-audio.md
- **Developed by:** [Alpha Scraper](https://apify.com/alpha-scraper) (community)
- **Categories:** Videos, Social media, Real estate
- **Stats:** 19 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### Pinterest Video Downloader - No Audio

The **Pinterest Video Downloader - No Audio** is an Apify Actor for extracting publicly accessible Pinterest video and image information from one or multiple Pinterest URLs. It accepts Pinterest links such as standard pin URLs and `pin.it` links, processes the supplied URLs, and returns structured metadata together with available media URLs.

The Actor is designed for users who need Pinterest video data in a structured dataset rather than manually opening pins and collecting information one by one. Each processed URL can return the pin ID, media type, title, description, webpage URL, uploader information, engagement statistics, media dimensions, duration, resolution, thumbnail, and available video or image URLs.

You provide one or more Pinterest URLs through the `startUrls` input. The Actor then processes those URLs and stores one result per input in the Apify dataset. When an individual URL cannot be processed, the result can include an `error` field so that successful and unsuccessful inputs can be distinguished.

> **Important:** Despite the Actor name containing “No Audio,” the current implementation does not modify or strip audio from source video streams. It extracts available video formats and their URLs; it does not create a separate silent video file.

### What Is the Pinterest Video Downloader - No Audio?

The **Pinterest Video Downloader - No Audio** is primarily a Pinterest media data extraction tool. Its user-facing workflow is straightforward: submit Pinterest video or pin URLs, run the Actor, and receive structured records for the supplied URLs.

The Actor can recognize whether the extracted media is being treated as a video or image and builds a consistent output structure around the available Pinterest information. For videos, the output can include one or more available video formats with quality, URL, dimensions, and duration information. For images, the result can include an image URL and its dimensions.

This makes the Actor useful when the goal is to collect Pinterest pin metadata and media references at scale through an Apify dataset.

### Key Features

| Feature                  | Description                                                                     | User Benefit                                    |
| ------------------------ | ------------------------------------------------------------------------------- | ----------------------------------------------- |
| Pinterest URL processing | Accepts one or multiple Pinterest URLs through `startUrls`                      | Process multiple pins in one run                |
| Video data extraction    | Identifies video media and returns available video format URLs                  | Collect video-oriented media references         |
| Image data extraction    | Handles image-based Pinterest content as well                                   | Use the same workflow for mixed media           |
| Pin metadata             | Returns identifiers, titles, descriptions, URLs, and timestamps where available | Build structured Pinterest datasets             |
| Uploader information     | Returns uploader ID and username/full name values when available                | Connect content with source accounts            |
| Engagement statistics    | Includes available repin, comment, like, and calculated save values             | Support content research and analysis           |
| Media metadata           | Returns width, height, resolution, thumbnail, and duration information          | Understand the media associated with each pin   |
| Error reporting          | Failed individual URLs can return an error record                               | Identify inputs that need review                |
| Apify dataset output     | Results are pushed to the Actor dataset                                         | Continue working with structured collected data |

### What Data Can You Extract?

The Pinterest video scraper returns information organized into several practical categories.

**Pin and content information** can include the Pinterest pin ID, media type, title, description, SEO title, creation/upload date, domain or extractor label, and webpage URL.

**Uploader information** can include the uploader ID, username, and full name. The follower count field is present in the output structure, although the current implementation uses `0` when a follower count is not supplied by the extracted source data.

**Engagement information** can include repin count, comment count, like count, and total saves. Total saves are represented as the combination of repins and likes in the generated result.

**Media information** can include thumbnail URLs, video format URLs, image URLs, width, height, duration, and resolution.

Some fields may be empty, zero, or unavailable depending on the Pinterest URL and the information returned for that particular pin. The Actor should therefore be treated as a structured extraction tool rather than a guarantee that every field is populated for every URL.

### Why Use This Actor?

Manual Pinterest data collection becomes repetitive when working with multiple pins. The Actor provides a repeatable URL-based workflow where users can submit a list of Pinterest links and receive structured records in a dataset.

The main practical advantages are consistency and organization. Instead of manually copying a title, URL, uploader, media reference, and engagement values from each page, the Actor organizes these values into a predictable result structure.

It can also be useful for workflows where Pinterest media metadata needs to be collected first and analyzed later. Because each input URL produces a corresponding dataset record, users can inspect successful results, identify errors, and continue processing their collected data.

### Benefits

The **Pinterest Video Downloader - No Audio** can support several data-oriented workflows:

- **Automation:** Process multiple Pinterest URLs as part of a repeatable Apify workflow.
- **Structured data collection:** Store pin information in consistent JSON-like records.
- **Pinterest research:** Collect content metadata for market, trend, or competitor research.
- **Media analysis:** Review available video or image URLs alongside dimensions and duration.
- **Dataset creation:** Build a reusable Pinterest dataset from supplied public URLs.
- **Content discovery:** Organize titles, descriptions, uploader details, and media information.
- **Error review:** Identify individual URLs that returned an error rather than silently losing them.

### How to Use the Pinterest Video Downloader - No Audio

The Actor uses a simple input-to-output workflow:

- Add one or more Pinterest URLs to the `startUrls` input.
- Make sure every entry contains a valid URL value.
- Start the Actor run.
- The Actor processes the submitted Pinterest links.
- Review the returned records in the Apify dataset.
- Use the structured output for research, analysis, dataset creation, or another compatible workflow.

The input can contain multiple URL entries, allowing you to process more than one Pinterest pin during the same run.

### Input

The Actor has one required input property: `startUrls`.

| Field       | Type  | Required | Description                                                  |
| ----------- | ----- | -------- | ------------------------------------------------------------ |
| `startUrls` | Array | Yes      | A list of one or more Pinterest video or pin URLs to process |

The input is configured as a request-list source, so each entry is represented as an object containing a `url` property. The Actor also accepts string URL values when processing the input programmatically.

Supported examples include standard Pinterest pin URLs such as `https://www.pinterest.com/pin/.../` and short Pinterest URLs such as `https://pin.it/...`.

### Input Example

```json
{
  "startUrls": [
    {
      "url": "https://pin.it/16JuGgSW4"
    },
    {
      "url": "https://www.pinterest.com/pin/934145147739555097/"
    }
  ]
}
```

Only the `startUrls` property is required by the supplied Actor configuration. No username, keyword, account login, API key, proxy setting, or other user-configurable field is defined in the public input schema.

### Output

Each processed URL produces a structured dataset record. Successful records contain the extracted Pinterest information, while unsuccessful processing can produce a record containing the original URL and an `error` message.

For video media, the `downloads.video` array contains available video format entries. Each entry can include quality, media URL, width, height, and duration in milliseconds. A thumbnail reference is also included separately.

For image media, the `downloads.image` array can contain the image URL and image dimensions.

### Output Fields

| Field         | Description                                                                      |
| ------------- | -------------------------------------------------------------------------------- |
| `url`         | Original input URL supplied to the Actor                                         |
| `id`          | Extracted Pinterest pin or media ID                                              |
| `type`        | Detected media type such as `video` or `image`                                   |
| `title`       | Extracted title                                                                  |
| `description` | Extracted description                                                            |
| `seo_title`   | Full title value when available, otherwise the title                             |
| `created_at`  | Extracted upload/creation date when available                                    |
| `domain`      | Extractor/domain value associated with the result                                |
| `webpage_url` | Pinterest webpage URL associated with the extracted item                         |
| `uploader`    | Uploader information including ID, username, full name, and follower count field |
| `stats`       | Repin, comment, share, like, and total save values                               |
| `board`       | Board-related output structure                                                   |
| `downloads`   | Video, image, and thumbnail media references                                     |
| `duration`    | Media duration in seconds                                                        |
| `width`       | Media width                                                                      |
| `height`      | Media height                                                                     |
| `resolution`  | Resolution formatted as `widthxheight`                                           |
| `error`       | Error message when a URL cannot be successfully processed                        |

The `board` object contains `id`, `name`, `url`, and `privacy` fields in the current output structure. The current implementation initializes these values with empty values except for a `public` privacy value.

### Output Example

```json
{
  "url": "https://www.pinterest.com/pin/934145147739555097/",
  "id": "934145147739555097",
  "type": "video",
  "title": "Pinterest video example",
  "description": "Example Pinterest pin description",
  "seo_title": "Pinterest video example",
  "created_at": "20250115",
  "domain": "Pinterest",
  "webpage_url": "https://www.pinterest.com/pin/934145147739555097/",
  "uploader": {
    "id": "example_user",
    "username": "example_user",
    "full_name": "Example User",
    "follower_count": 0
  },
  "stats": {
    "repin_count": 12,
    "comment_count": 3,
    "share_count": 0,
    "like_count": 25,
    "total_saves": 37
  },
  "board": {
    "id": "",
    "name": "",
    "url": "",
    "privacy": "public"
  },
  "downloads": {
    "video": [
      {
        "quality": "1080p",
        "url": "https://example.com/video.mp4",
        "width": 1920,
        "height": 1080,
        "duration_ms": 15000
      }
    ],
    "thumbnail": "https://example.com/thumbnail.jpg"
  },
  "duration": 15,
  "width": 1920,
  "height": 1080,
  "resolution": "1920x1080"
}
```

The URLs above are illustrative placeholders showing the output structure; actual returned media URLs depend on the Pinterest content being processed.

### Use Cases

The Actor is suitable for workflows that begin with known Pinterest URLs.

- **Pinterest content research:** Collect titles, descriptions, uploader details, engagement values, and media information.
- **Video research:** Gather available Pinterest video format URLs and associated metadata.
- **Content cataloging:** Create structured records for Pinterest pins collected from selected sources.
- **Competitive research:** Compare publicly accessible pin metadata across a manually selected set of URLs.
- **Media dataset creation:** Assemble Pinterest video and image references for later analysis.
- **Trend research:** Organize public pin metadata into a dataset for subsequent review.
- **Automation workflows:** Run URL-based Pinterest extraction repeatedly through Apify.

### Advantages

The Actor combines a simple input model with a relatively rich output structure. Users only need to provide Pinterest URLs, while the resulting records organize content, uploader, statistics, and media information under consistent fields.

Another advantage is support for mixed Pinterest content. The extraction logic can classify an item as either video or image and adjust the media-related output accordingly.

The dataset-oriented structure is also useful for downstream processing because every result includes the original submitted URL, making it easier to relate extracted information back to the source.

### Limitations

- The Actor requires Pinterest URLs; it is not configured as a keyword, username, profile, board-search, or general Pinterest search scraper.
- The input schema defines only `startUrls`, so there are no public settings for selecting domains, regions, maximum item counts, or other filters.
- Available metadata varies by Pinterest content. Some fields may be empty or zero.
- Follower information is not reliably populated and may remain `0`.
- Board metadata is currently represented by a fixed output structure and may not contain populated board details.
- The Actor returns media URLs and metadata rather than documenting a separate user-facing audio-removal process.
- Individual URLs may return an `error` field when extraction is unsuccessful.

### Pros and Cons

| Pros                                                    | Cons                                                                        |
| ------------------------------------------------------- | --------------------------------------------------------------------------- |
| Supports multiple Pinterest URLs in one run             | Requires specific Pinterest URLs rather than keyword discovery              |
| Returns structured pin and media metadata               | Some metadata fields may be unavailable                                     |
| Handles video and image media                           | Does not provide user-configurable filters in the current input schema      |
| Includes available video format URLs                    | Returned media availability depends on the source                           |
| Preserves failed URL information through an error field | “No Audio” does not mean returned source videos are guaranteed to be silent |

### Comparison With Alternative Approaches

| Capability                 | This Actor                            | Manual / Typical URL-Based Approach             |
| -------------------------- | ------------------------------------- | ----------------------------------------------- |
| Multiple Pinterest URLs    | Supported                             | Usually requires repeated manual work           |
| Structured dataset records | Supported                             | Often requires manual formatting                |
| Pin metadata collection    | Supported                             | Manual copying may be required                  |
| Video format references    | Supported when available              | Must generally be located and recorded manually |
| Image information          | Supported                             | Usually collected separately                    |
| Error visibility           | Individual results can contain errors | Manual workflows may track failures separately  |
| Repeatable Apify workflow  | Supported                             | Typically less automated                        |

This comparison focuses on workflow characteristics rather than performance claims about other tools.

### Best Practices

For reliable use of the **Pinterest Video Downloader - No Audio**, start with a small set of Pinterest URLs and inspect the resulting dataset before processing a larger collection.

Use complete, valid Pinterest links and verify that your `startUrls` entries contain the expected `url` property. When collecting a mixed group of pins, review the `type` field so that video and image records can be handled appropriately.

Because metadata availability can vary, validate important fields before using them in downstream analysis. For video results, inspect the `downloads.video` array and confirm that the returned format and dimensions meet your workflow requirements.

### Troubleshooting

**Invalid Input:** Confirm that `startUrls` is present and contains URL entries. Each request-list item should provide a valid `url`.

**Empty Results:** Check that the supplied links are valid Pinterest URLs and that the source content can be accessed publicly. Testing one URL at a time can help isolate the issue.

**Partial Results:** A run can contain successful records alongside failed records. Check each result for the presence of an `error` field rather than assuming every submitted URL was processed successfully.

**Missing Fields:** Some metadata is dependent on the information available for the particular Pinterest item. Empty strings or zero values do not necessarily indicate a formatting problem.

**Video Data Not Available:** Confirm the returned `type` and inspect `downloads.video`. A Pinterest URL that does not expose usable video information may instead be classified as an image or return an error.

**Media URL Issues:** Treat returned media URLs as source references and validate them before building downstream processes that depend on continued accessibility.

### Frequently Asked Questions

**What does the Pinterest Video Downloader - No Audio do?**
It extracts publicly accessible Pinterest video or image information from supplied Pinterest URLs and returns structured records in the Apify dataset.

**Can I process multiple Pinterest URLs?**
Yes. The required `startUrls` field is an array, so multiple Pinterest URLs can be submitted in the same run.

**What input format does the Pinterest Video Downloader use?**
The configured input expects request-list entries containing a `url` property. Pinterest `pin.it` links and standard Pinterest pin URLs are supported by the current processing logic.

**What data does the Pinterest Video Downloader return?**
Depending on source availability, results can include pin ID, type, title, description, webpage URL, uploader information, engagement statistics, thumbnails, media URLs, duration, dimensions, and resolution.

**Does it download a silent video without audio?**
The current implementation does not strip or remove audio from a source video. It extracts available video format URLs and metadata, so “No Audio” should not be interpreted as a guarantee that every returned video stream is silent.

**Does the Actor scrape Pinterest profiles or search results?**
The configured input is URL-based and is intended for supplied Pinterest URLs. It is not documented as a Pinterest profile, keyword, or search-results scraper.

**What happens when one Pinterest URL fails?**
A failed URL can return a result containing the original `url` and an `error` field. This allows unsuccessful inputs to be identified separately from successful records.

**Why are some values empty or zero?**
Certain Pinterest metadata is not always available. The output structure can therefore contain empty strings or zero values for fields that were not provided by the source data.

**Can I use the results for research and datasets?**
Yes. The structured records are suitable for organizing publicly accessible Pinterest metadata and media references for research, analysis, and dataset-building workflows.

**What is the best way to start?**
Begin with a small number of valid Pinterest URLs, run the Actor, inspect the dataset, and then expand your input list after confirming that the returned fields match your workflow.

### NLP Keywords

- Pinterest video downloader
- Pinterest video scraper
- Pinterest video data extractor
- Pinterest media scraper
- Pinterest pin scraper
- Pinterest video URL extractor
- Pinterest pin data extraction
- Pinterest video metadata
- Pinterest image scraper
- Pinterest media downloader
- Pinterest content extraction
- Pinterest public data scraper
- Pinterest video metadata extractor
- Pinterest pin metadata
- Pinterest media URL extraction
- Pinterest content data
- Pinterest dataset extraction
- Pinterest video research
- Pinterest pin information
- Pinterest structured data

### Related Keywords

- download Pinterest video
- scrape Pinterest videos
- extract Pinterest video URL
- Pinterest video link scraper
- Pinterest pin URL scraper
- Pinterest media data extraction
- Pinterest video information
- Pinterest video metadata scraper
- Pinterest public pin scraper
- Pinterest image and video scraper
- Pinterest content scraper
- Pinterest pin information extractor
- Pinterest media URL scraper
- Pinterest video dataset
- Pinterest pin data scraper
- Pinterest video research tool
- Pinterest media extractor
- Pinterest pin metadata scraper
- scrape Pinterest pin URLs
- Pinterest video data collection

### Final Overview

The **Pinterest Video Downloader - No Audio** provides a URL-based way to collect structured Pinterest video and image information through Apify. Submit one or more Pinterest URLs, run the Actor, and review the resulting dataset for pin metadata, uploader information, engagement statistics, media references, dimensions, duration, and resolution.

Its strongest fit is for users who already have Pinterest URLs and need a repeatable way to turn those links into structured records. Because source metadata and media availability can vary, reviewing the resulting dataset and handling error records is an important part of production workflows.

The Actor focuses on publicly accessible Pinterest content and does not require additional user-configurable input beyond the required `startUrls` list.

*Contact me:* <Alphascraper69@gmail.com>

# Actor input Schema

## `startUrls` (type: `array`):

List of one or more Pinterest video URLs

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://pin.it/16JuGgSW4"
    },
    {
      "url": "https://www.pinterest.com/pin/934145147739555097/"
    }
  ]
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "startUrls": [
        {
            "url": "https://pin.it/16JuGgSW4"
        },
        {
            "url": "https://www.pinterest.com/pin/934145147739555097/"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("alpha-scraper/pinterest-video-downloader-no-audio").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "startUrls": [
        { "url": "https://pin.it/16JuGgSW4" },
        { "url": "https://www.pinterest.com/pin/934145147739555097/" },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("alpha-scraper/pinterest-video-downloader-no-audio").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "startUrls": [
    {
      "url": "https://pin.it/16JuGgSW4"
    },
    {
      "url": "https://www.pinterest.com/pin/934145147739555097/"
    }
  ]
}' |
apify call alpha-scraper/pinterest-video-downloader-no-audio --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alpha-scraper/pinterest-video-downloader-no-audio"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/4oLxuGjFHiw7qIwP5/builds/gzZU98giMI18odY7J/openapi.json
