# Website to Markdown — Clean Content for AI & LLMs (`hipersoft/web-to-markdown`) Actor

Turn any web page into clean Markdown — stripped of nav, ads and boilerplate — ready to feed an LLM, RAG pipeline or n8n AI workflow. Article text, title and metadata from a URL.

- **URL**: https://apify.com/hipersoft/web-to-markdown.md
- **Developed by:** [hiper soft](https://apify.com/hipersoft) (community)
- **Categories:** Developer tools, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.0015 / page converted

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

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Website to Markdown — Clean Content for AI, LLMs & n8n

**Turn any web page into clean Markdown** — stripped of navigation, ads and boilerplate — ready to feed an LLM, a RAG pipeline, or an AI step in an n8n / Make workflow. Give it a URL and get back the article title, body as Markdown, and metadata.

![Website to Markdown input — configure the options in the Apify Console](https://api.apify.com/v2/key-value-stores/SUfvnaFLd9z9eBCtV/records/web-to-markdown-input.png)

### What it does

- Extracts the **main article content** (readability) and converts it to **Markdown**.
- Returns **title, byline, excerpt and word count**.
- Optional: keep or strip **links** and **images**.
- Saves a `.md` file per page and puts the Markdown right in the dataset (easy to pipe into an LLM node).

### Use cases

- **AI / RAG pipelines** — clean text to embed or summarize (perfect for n8n AI Agent / LangChain nodes).
- **Content archiving** — save readable copies of articles.
- **Summarize / repurpose** — feed clean Markdown to an LLM for summaries or rewrites.

### Input

```json
{ "urls": ["https://example.com/blog/post"], "includeLinks": true, "includeImages": true }
```

| Field | Type | Description |
|---|---|---|
| `urls` | array | Pages to convert. |
| `html` | string | Optional raw HTML instead of URLs. |
| `includeLinks` | boolean | Keep hyperlinks. |
| `includeImages` | boolean | Keep image references. |

### Output

![Website to Markdown output — the results as a clean dataset](https://api.apify.com/v2/key-value-stores/SUfvnaFLd9z9eBCtV/records/web-to-markdown-output.png)

```json
{ "url": "https://example.com/blog/post", "title": "My Post", "wordCount": 812, "markdown": "# My Post\n\n...", "resultUrl": "https://api.apify.com/v2/key-value-stores/.../records/page-0001.md" }
```

#### Output schema

| Field | Type | Description |
|---|---|---|
| `url` | string (URL) | The source page. |
| `title` | string | Article title. |
| `wordCount` | integer | Words in the Markdown. |
| `resultUrl` | string (URL) | Link to the Markdown file. |

### FAQ

**Great for LLMs?** Yes — the Markdown drops the page chrome so you feed the model only the real content (fewer tokens, better answers).

**Can I use it in n8n?** Yes — run it from the Apify node and pass the `markdown` field to your AI/LLM step. It also works with [Make, Zapier and other integrations](https://apify.com/integrations) and the [Apify API](https://docs.apify.com/api/v2).

### Notes

Original clean-room implementation. Collects only public page content.

# Actor input Schema

## `urls` (type: `array`):

Web pages to convert to clean Markdown. One Markdown file per URL.

## `html` (type: `string`):

Optional: convert this raw HTML instead of fetching URLs.

## `includeLinks` (type: `boolean`):

Keep hyperlinks in the Markdown.

## `includeImages` (type: `boolean`):

Keep image references in the Markdown.

## Actor input object example

```json
{
  "urls": [
    "https://example.com/blog/post",
    "https://news.site/article"
  ],
  "includeLinks": true,
  "includeImages": true
}
```

# Actor output Schema

## `results` (type: `string`):

The results as dataset items.

# 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 = {
    "urls": [
        "https://en.wikipedia.org/wiki/Web_scraping"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("hipersoft/web-to-markdown").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 = { "urls": ["https://en.wikipedia.org/wiki/Web_scraping"] }

# Run the Actor and wait for it to finish
run = client.actor("hipersoft/web-to-markdown").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 '{
  "urls": [
    "https://en.wikipedia.org/wiki/Web_scraping"
  ]
}' |
apify call hipersoft/web-to-markdown --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hipersoft/web-to-markdown"
        }
    }
}

```

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/LQcC1bZ0QgJAbDbip/builds/srEJOIeRLGOkP4t5h/openapi.json