Determine the Best Method to Upload Assets to your Asset Bank

Sara Anthony
Sara Anthony
  • Updated

Uploading assets to Bynder is vital in maintaining an up-to-date and easily discoverable Asset Bank. Whether migrating assets to Bynder for the first time or regularly expanding your library, selecting the right upload method is key to ensuring efficiency and organization.

This guide explores Bynder's various upload methods, highlighting their use cases and features to help you choose the one that best suits your needs. From small-scale, self-service uploads to large-scale migrations and automated workflows, Bynder offers flexible options tailored to different scenarios.

No matter which method you select, the asset upload process involves two critical steps:

  • Applying Relevant Metadata: Metadata is essential for organizing assets and making them easily discoverable within the DAM.
  • Storing Assets in the Asset Bank: Properly storing uploaded assets ensures they are accessible to users and seamlessly integrated into workflows.

Choosing the right upload method ensures your Asset Bank remains well-organized, highly discoverable, and an invaluable resource for your users.

Overview of Upload Methods

Upload Method Best For Key Features
Front Uploader Small to medium uploads Drag and drop up to 250 assets. Suitable for self-service uploads.
External Uploader External collaborators Allows non-DAM users to upload assets. Requires admin approval before storage in the DAM.
Mass Uploader Large-scale uploads Supports more than 250 assets per session. Assign unique metadata via a CSV.
Media Import System migrations It is ideal for migrations exceeding 5,000 assets. Bynder Platform Services handles metadata mapping and troubleshooting. 
Integrations & APIs Automated workflows Seamlessly connect with external systems like PIMs, CMS, or cloud storage providers.

Front Uploader

The Front Uploader is the most common upload method, offering a simple, user-friendly interface for smaller uploads.

  • Size: Ideal for small to medium uploads (up to 250 assets).
  • User Type: Logged-in users with upload permissions.
  • Use Case Example: A team member uploads a few newly designed logos for immediate campaign use.
  • Pro Tip: If you’re launching with fewer than 5,000 assets, the Front Uploader is an excellent tool for the initial setup.

External Uploader

The External Uploader is designed for non-DAM users, such as freelancers or agencies, who must contribute assets without directly accessing the DAM.

  • Size: Flexible, dependent on admin approval workflows.
  • User Type: External collaborators without DAM permissions.
  • Key Feature: Uploads are reviewed by admins before final storage.
  • Use Case Example: An agency uploads campaign assets for review and approval.

Mass Uploader

The Mass Uploader is perfect for bulk uploads, especially for large-scale projects.

  • Size: More than 250 assets per session.
  • Key Features:
    • Assign unique metadata to each asset via CSV.
    • Self-service tool for ongoing bulk uploads.
  • Use Case Example: The marketing team uploads hundreds of product images with unique tags and descriptions after a product photoshoot.
  • Consideration: Platform Services setup may be required for first-time use.

Media Import with SFTP or AWS S3

Media Import is tailored for large-scale migrations and is a great option if you transition assets from another system to Bynder. Use Secure File Transfer Protocol for high-volume, secure uploads.

  • Best For: Migrations involving over 5,000 assets or existing metadata from a legacy system.
  • Key Features:
    • Managed by Bynder’s Platform Services team.
    • Handles troubleshooting and ensures metadata accuracy.
  • Pro Tip: Use this method for smooth transitions during initial migrations

Integrations & APIs

Integrations and APIs streamline workflows by connecting Bynder with external systems like PIMs, CMS, or cloud storage solutions.

  • Best For: Automated uploads and system integrations.
  • Key Features:
    • Continuous sync with cloud storage (Google Drive, Box, Dropbox).
    • Custom scripts for repeatable uploads.
  • Use Case Example: A marketing team uses an Adobe Creative Cloud integration to sync their latest designs directly into the DAM.
  • Consideration: Requires technical resources to write and manage API scripts.

Work with a Bynder Certified Partner

If your team does not have a dedicated DAM resource or has complex upload needs, working with a Bynder Certified Partner is an excellent option.

  • Size: Large migrations (5,000+ assets) or multi-environment setups.
  • User Type: Organizations with limited internal resources or expertise.
  • Key Benefits:
    • Expert support for metadata mapping and troubleshooting.
    • Handles multiple hosting environments or complex setups.
    • Perfect for scaling and optimizing the upload process.
  • Use Case Example: A company migrating over 10,000 assets from multiple legacy systems while requiring metadata mapping.

Additional Upload Methods

Permissions Specific to Uploading

Your ability to upload assets depends on your Bynder portal configuration and user permissions.

  • Heavy Users: You can upload it directly to the DAM without additional approval.
  • Regular Users: You can upload it directly to the DAM but may need additional approval from the Admin.
    • Audit upload requests - Allows users to audit upload requests in the waiting room.
  • Light Users: May upload assets requiring admin approval before storage.
    • Upload assets with mandatory approval—This option allows users to upload assets for approval. An administrator must approve all uploads.
  • External Users: Use the External Uploader to contribute assets.

Pro Tips for Upload Success

  • Organize Metadata
    Fill out metadata fields accurately before uploading assets. A well-organized metadata structure enhances asset discoverability and makes it easier for users to find what they need quickly.
  • Search for Existing Assets
    Always search the system before uploading a new asset. This will help prevent duplication and ensure you’re not uploading something already in the DAM. If enabled, utilize the "similar search" functionality to double-check if the asset already exists in the system.
  • Use Duplicate Manager
    Leverage the Duplicate Manager to identify and avoid uploading duplicate assets. This proactive step helps maintain a clean and organized DAM, reducing the need for future cleanup efforts.
  • Collaborate with Admins
    Work closely with DAM administrators to configure permissions and streamline upload workflows. Admins can help set up access controls and workflows, ensuring a smooth and efficient upload process.
  • Plan Ahead
    Consider the best upload method for your specific needs. Whether you’re uploading in bulk or individually, choosing the right approach ahead of time will save you valuable time and help minimize the potential for errors.
Share