> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-import/how-to-import-with-images-from-url.md).
# How to import with images from url
Learn how to import with images by using URL's of media from the web
## Before importing
A prerequisite to importing entities with images is having an excel spreadsheet with the data organized in named columns. For this tutorial we have a made a simple spreadsheet containing information internal ids of products and URL's of images from the web.
Spreadsheet with data and headers
By importing URL's of images from the web into an AssetReferenceAttribute the PIM will automatically download the image and upload it to Struct PIM 4.
Notice how cell B2 contains two URL's separated by a ";". This is because we are importing into an AssetReferenceAttribute with 'Allow multiple assets' enabled. In this case the ";" acts as a delimiter and each URL will be imported as one picture into the attribute.
## Starting the import
To start importing you choose the excel spreadsheet with the data you want to import, in this tutorial the spreadsheet is called "import\_with\_images\_url.xlsx".
Next you need to choose the correct Import type. Choose the one that fits what you need to import. In this tutorial we are importing to an AssetReferenceAttribute, so we choose "General Except Import".
Since we are using images from the web we do not enable "Upload assets".
Import page
Having chosen the file you want to import and the import type, click 'Start upload' to continue.
## Mapping your data
Mapping data works the same way as it does without media.
If you are uncertain on how to do this you can follow read more about this in earlier import-tutorials:
Mapping with General excel import: [How to import products](/tutorials/guides/how-to-use-import/how-to-import-products.md)\
Mapping with List property import: [How to import data into a list property on entities](/tutorials/guides/how-to-use-import/how-to-import-list-data-using-list-property-import.md)
Data mapping
One difference however is that this is where you will choose the folder to upload your images to. This is done by selecting the folder in the list under 'Select upload folder'.
{% hint style="warning" %}
**Note** Be aware that 'Select upload folder' will not be visible until an asset reference attribute has been chosen to be mapped to.
{% endhint %}
## Approve changes
When approving data you should be able to see the media files being attached to your entity.
If you are happy with the changes, approve them and click 'Commit import' to finalize the import.
---
# 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.struct.com/tutorials/guides/how-to-use-import/how-to-import-with-images-from-url.md?ask=&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.
