> For the complete documentation index, see [llms.txt](https://docs.webstudio.is/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.webstudio.is/university/foundations/copy-paste/markdown.md).

# Markdown

Pasting Markdown automatically adds the respective components.

Copy Markdown and paste it into Webstudio, and it will automatically add all the components, such as headings, images, and links.

{% hint style="info" %}
Many tools use Markdown behind the scenes, letting you copy directly from the editor.
{% endhint %}

Example sources and Markdown flavors:

* Standard Markdown
* GitHub-flavored Markdown
* Notion
* SurferSEO
* Obsidian
* Coda

If the pasted Markdown references images, Webstudio uploads those images into [Assets](https://docs.webstudio.is/university/foundations/assets.md) and rewrites the generated image instances to use the uploaded assets.

Want to embed Markdown? See [Markdown Embed](https://docs.webstudio.is/university/core-components/markdown-embed.md).

## Related

* [CSS](https://docs.webstudio.is/university/foundations/copy-paste/css.md) – Paste CSS to populate the Style Panel
* [Referenced images](https://docs.webstudio.is/university/foundations/copy-paste/images.md) – Understand image handling during paste
* [Webflow](https://docs.webstudio.is/university/foundations/copy-paste/webflow.md) – Copy Webflow components into Webstudio
* [Shortcuts](https://docs.webstudio.is/university/foundations/shortcuts.md) – Keyboard shortcuts for faster workflows
* [Commands and search](https://docs.webstudio.is/university/foundations/commands-and-search.md) – Quick access to commands and settings
* [Anatomy of the Webstudio builder](https://docs.webstudio.is/university/foundations/anatomy-of-the-webstudio-builder.md) – Overview of the Webstudio interface


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.webstudio.is/university/foundations/copy-paste/markdown.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
