> ## Documentation Index
> Fetch the complete documentation index at: https://docs.figr.design/llms.txt
> Use this file to discover all available pages before exploring further.

# Understand Url

> Share any link and Figr reads the content. Extract information from articles, documentation, product pages, or any webpage to inform your work.

## [​](#what-understand-url-does) What Understand URL Does

Understand URL reads and extracts content from any webpage you share. It processes the text, information, and context on the page, not the visual design. Understand URL extracts:

* Page content and copy
* Article text and information
* Documentation and guides
* Product descriptions
* Feature lists and specifications
* Any textual content

<Tip>
  **Important:** This tool is for content extraction, not visual reference. For visual design reference from a webpage, use the [Chrome Extension](/designing/input/chrome-extension) instead.
</Tip>

## [​](#when-figr-uses-understand-url) When Figr Uses Understand URL

Figr engages URL understanding when you:

* Paste a link in the query box
* Ask Figr to read or analyze a page
* Need content from a webpage as context
* Reference documentation or articles
* Share competitor product pages for information

## [​](#content-vs-visual)Content vs. Visual Reference

| **Understand URL (Content)**   | **Chrome Extension (Visual)**      |
| ------------------------------ | ---------------------------------- |
| Reading article content        | Capturing visual design patterns   |
| Extracting product information | Extracting colors, spacing, layout |
| Understanding documentation    | Referencing UI component styles    |
| Getting text-based context     | Matching visual design language    |

## [​](#best-practices)Best Practices

<AccordionGroup>
  <Accordion title="Use Full URLs">
    Provide complete links: "Read [https://docs.stripe.com/webhooks](https://docs.stripe.com/webhooks)" rather than "Look at Stripe's webhook docs"
  </Accordion>

  <Accordion title="Specify What You Need">
    Focused extraction:

    * "Read \[URL] and extract the feature list"
    * "Look at \[URL] and summarize the pricing tiers"
    * "What does \[URL] say about their API limits?"
  </Accordion>

  <Accordion title="Combine with Design Requests">
    Content-informed design:

    * "Read this documentation \[URL], then design an interface for the workflow it describes"
    * "Extract the requirements from \[URL] and create a PRD, then design the feature"
  </Accordion>

  <Accordion title="For Visual Reference, Use Chrome Extension">
    If you want to match styling:

    * **Don't**: "Look at \[URL] and match their design"
    * **Do**: Capture the page with Chrome extension, then reference the visual capture
  </Accordion>
</AccordionGroup>