Upload multiple product images in a single batch queue.
Product image links
Keep product images mapped to the right products
Once a catalogue grows beyond a few products, image handling can get messy very quickly. One item has a front photo, another has three detail shots, and the files are sitting across local folders with names that no longer make sense. The problem becomes more obvious when a spreadsheet or marketplace asks for an image URL instead of a file from your computer.
Media2URL gives each completed product image its own hosted URL. You can upload several images together, check the result for each file, keep the originals organised in the Media Library, then copy the correct direct image URL into the product row or catalogue field that needs it.
For a catalogue batch, use the bulk product image upload workflow. For one photo, the single image URL tool creates a hosted link for the product field.
File preparation
Get the filenames right before the upload starts
A batch of twenty images is easy to manage when the names already tell you what belongs where. The same batch becomes confusing when the files are called IMG_4012.jpg, final new.jpg and copy 3.jpg.
A name such as SKU 4821 front.jpg gives you something useful to match against the catalogue later. If one product has several views, keep the same product code in each filename and change the last part, for example SKU 4821 front.jpg, SKU 4821 back.jpg and SKU 4821 detail.jpg.
This becomes more important as the catalogue grows. Clear names give you a way to check the upload result without opening every image just to work out which product it belongs to.
Queue management
Bulk upload saves time, but it does not decide the catalogue mapping
The bulk uploader lets you send several supported product images in one queue. Each completed image still has its own result and its own URL.
That distinction is important. The batch does not become one combined file, and Media2URL does not automatically fill the matching row in your product sheet.
Keep the product ID beside the filename in your spreadsheet or catalogue data. Once the queue finishes, check the image and filename together, then place the direct URL into the correct row.
This check also catches a problem that is easy to miss in a large upload. Some files can finish while another item fails, so a mostly successful batch should not be treated as proof that every selected image completed.
Output types
Use the image URL that the destination is actually asking for
A Media2URL share page is made for a person opening the file in a browser. A product image field normally needs the hosted image itself. Use the direct image URL from Image to Link or Bulk Image Upload when the catalogue field expects an image source.
The final store still needs testing. A valid Media2URL image URL can open correctly in a browser while an external marketplace has its own rules about remote images.
| Where you are using the image | What to start with |
|---|---|
| Product or catalogue image field | Direct image URL |
| Spreadsheet row that expects an image source | Direct image URL |
| Human review before publishing | Share page where useful |
| Several local product images at once | Bulk Image Upload |
Marketplace compliance
Marketplace rules still come from the marketplace
Media2URL hosts the image. Shopify, eBay, Amazon and other destinations decide what they accept on their own side.
That can include image dimensions, aspect ratio, format requirements or other listing rules. Check those requirements before preparing a large product batch, because uploading the wrong shape first only creates more work later.
If a marketplace expects a square crop, another size or a cleaner version of the image, prepare it in the Image Editor before you place the final URL into the listing.
The same rule applies after publishing. Open the real product page and make sure the destination is rendering the remote image correctly rather than assuming everything is fine because the URL worked in a separate browser tab.
Workflow distinction
Bulk Image Upload and Batch Image Processing solve different jobs
These two workflows sound similar, but they are useful at different stages.
Bulk Image Upload takes several local product files and creates Media2URL assets with individual results and direct URLs.
Batch Image Processing works on existing uploaded media and applies the same resize, crop or format preset across a group of images.
That difference becomes useful when a catalogue needs 100 images uploaded first, then the same crop or output treatment applied across the set. Uploading and processing are separate jobs even when they happen as part of the same catalogue update.
Master source management
Keep the source photo before creating marketplace versions
A marketplace crop should not become the only copy of a useful product photo.
Keep the original high resolution image in the Media Library, then create the version needed for the current channel. If another marketplace asks for a different ratio later, you still have the source rather than starting from an already cropped image.
Folders and tags can also help separate product ranges, seasons or collections where those controls are available.
This is especially helpful when packaging or product photography changes. Keeping the old and new sets clearly separated reduces the chance of linking an outdated product image back into active inventory.
Catalogue update steps
A normal catalogue update can look like this
New product range
A new product range arrives with several images for every SKU. The files are named with the product code and angle before upload, then added through Bulk Image Upload. Once the queue finishes, each result is checked against the filename. The direct URL goes into the matching catalogue row only after the product and image have been confirmed.
Seasonal change
A seasonal change is simpler. Only the affected products need new images, so the fresh files can stay in their own clearly named folder while the previous versions remain separate until the live catalogue has been checked.
Marketplace launch
For a marketplace launch, the preparation comes first. Crop or resize the image according to the destination rules, keep the source available, then place the final direct URL into the listing where externally hosted images are accepted.
Workflows
Product image workflows that fit this setup
- Online stores that need hosted image URLs for product or catalogue fields.
- Marketplace sellers preparing several product images before adding them to external listings.
- Catalogue teams working from spreadsheets where product rows need matching image URLs.
- Small e commerce teams keeping original product images organised for future range or seasonal updates.
Checklist
Before changing a live catalogue
- Check failed uploads separately. One failed image can be hidden inside an otherwise successful batch.
- Match the filename, product ID and completed image before pasting the URL into the catalogue.
- Check the destination's current image rules before preparing a large group of files.
- Open the final listing after the update, because every external catalogue or marketplace handles remote images in its own way.
Questions
Frequently asked questions
Yes. Bulk Image Upload accepts multiple supported images and shows the progress and result for each item in the queue. File size, upload count and monthly limits still follow the current plan.
The current workflow is described as returning individual results for completed images. It does not automatically populate your catalogue CSV. Keep the product ID and filename mapping in your own spreadsheet, then place each completed direct URL into the matching row.
Yes. The workflow uses the filename as part of reviewing and matching completed items, which is why structured names such as SKU 4821 front.jpg are useful before the upload begins. Clear filenames become especially helpful when several images belong to the same product.
No. Media2URL hosts the images and gives you their URLs. You decide which URL belongs to each product and add it to Shopify, eBay, Amazon or another destination using the workflow that platform provides.
Use the direct image URL when the catalogue field expects the hosted image itself. A share page is meant for a person viewing the asset in a browser, so it is not the same thing as the raw image URL used by a product image field.
Yes. Supported product images can be prepared with the Image Editor before the final version is used in the catalogue. For larger groups that need the same resize, crop or format treatment, Batch Image Processing is the more suitable workflow.
Yes. A product can have separate front, back, detail or packaging images. Using the same SKU or product code in the filenames makes those files much easier to group and match later.
No. Marketplace requirements come from the destination itself, and those rules can differ between platforms. Check the current dimensions, aspect ratio and format requirements first, then prepare the image in Media2URL before using its URL in the listing.
Related tools
Explore product image & bulk tools
Direct URLs and Markdown tags for single hero images.
Organise product photos by brand, season, and SKU tags.
Square crops, background adjustments, and resizing presets.