Web-optimized File Formats

In our support article titled What Are The Supported File Formats, we list all the file types that can be uploaded into ConceptShare, and in the article What Are The Recommended Settings For My File Types, we outline reasonable limits and constraints for various asset types (ex. images, documents, videos, etc.)

It's important however, to make a distinction regarding file formats which are supported in ConceptShare and those which are generally optimized by design for use within web browsers. As an example, ConceptShare supports nearly two dozen different image formats as well as Office file formats (ex. Word Docs, PowerPoint, Excel, etc.), but web browsers have no idea how to display most of these file types. Therefore, when you upload files formats which browsers don't support, ConceptShare will first convert these files into a proxy format (such as JPEG for images, and PDF for documents) which the browser can display. In other cases, even among those formats supported by web browsers, there are file formats which may perform far better than others.

Now that you know ConceptShare will have to convert any file type that isn't supported for web browsers to those which are, you can take measures to ensure that the assets you upload are in a format which will deliver maximum visual quality while minimizing the file size. This is important because the choice of file formats has cascading effects down your entire review and approval chain.

Consider the following example:

Suppose you have a high resolution Photoshop image file which is 1000 MB. You have several options.

  1. PSD file format is supported by ConceptShare so just go ahead and upload the 1000 MB PSD file as-is
  2. First export the PSD file to flat image format like TIF which would shrink the file size down to 100 MB, and then upload the asset (better option)
  3. First, export the PSD file as a web optimized image format (ex. JPEG or PNG) which would likely shrink the file size down to 10 MB (best option)

Why go through the trouble?

  1. As the asset uploader, you spend far less time uploading each asset
    (think about how long it takes to upload 1000 MB file vs. a 10 MB file)
  2. As a reviewer, you'll spend equally less time waiting to download the unnecessarily large asset for viewing and reviewing

In such a case, the visual quality can be kept indistinguishable; only the uploader and reviewer's wait times are reduced and their experience positively impacted.

If we take the above example and apply the time savings at scale, we see a fairly significant increase in efficiency. The choice of selecting the best formats saves everyone's time and improves the user experience for everyone involved in the process. As such, when given the choice, try to upload web-friendly file formats such as:

  • JPEG/PNG for images
  • Simple PDFs for documents
  • Video and Audio as described below

Not only are you helping improve your team's experience and efficiency, but by making your processes more efficient, you're reducing entropy, using less resources, and helping save a few trees. For that, we are grateful :)


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request