FileMaker Image Management – Container Field Behavior and Much More

One of my clients called this week and told me his logo got inverted when printing to a PDF. Also, the PDF file size doubled. Previously it did not occur to me to check the file he received from his designer, because I wrongfully assumed the designer gave him the appropriate file. But this brings up some interesting points about what files we should use with FileMaker and how we should use them. So, I gathered some useful information. Hope this helps you with handing your images in FileMaker and FileMaker Go.

General Image Handling

There are several different ways you can show images on a FileMaker layout:

  • Container field (Insert/Picture)
  • Place image on the layout (copy and paste from another source)
  • Show from another source in a webviewer (i.e. using SuperContainer or DocuBin)

1. Container Field


  1. Quick and easy. You insert an image, and voila it’s right there. If you store the file as a reference only  (suggested use if you have constant access to the hard drive the files reside on and do not plan to move or delete them) you will not bloat your database;
  2. Anyone can export it from there by right-clicking on the image and choosing “Export Field Contents”;
  3. The image can be swapped out just by inserting another image;
  4. Scan directly into a container field (by using a plug-in);
  5. You can export or email the image (file) as an attachment;
  6. Images can be cropped or resized (pay attention to maintaining proportion).


  1. You cannot do too much manipulation without a plug-in;
  2. Your database file size gets large by every image you inserted (unless stored as a reference only), therefore eventually your database will get slower;
  3. Global container fields save on close, so your file must be accessed locally, if you’d like to save a change;
  4. You can’t find or sort records, so you need to set up a calc field. See Exhibit A;
  5. You can only print the image as it is on the layout.

2. Place Image on Layout: Placing an image on the layout is not generally a good idea, unless it is your logo or  layout design (i.e. you are creating a header), but even so it’s best to use a global container field in an interface table or an image table where you load the images from when your database starts. Although, I have to mention that I see image quality differences between a referenced image in a field vs. an image pasted on the layout: in my opinion, image quality of the pasted image will be superior.

3 . Web Viewer

  • Web viewers are great for images. You can show images from a website or SuperContainer. PDF (and certain image*) files can be viewed from a web viewer. PDFs can even be manipulated (zoom, next page, etc.) on Macs. Files are not stored in the FileMaker database.
  • You cannot print from the web viewer.  You can print the layout, but that’s agains, any decent designer’s instincts.
  • There’s a great article by Geoff Coffey on Scaling Images in a Web Viewer.

Instant Web Publishing

  • Container field data cannot be entered or modified from IWP.
  • Complex or layered pictures are not rendered properly.
  • SuperContainer works with IWP.

Image Management Helpers (Plug-Ins and Tools)

  • SuperContainer (File and image management. The images are NOT stored in the FileMaker database, rather stored on a file server (can be your local computer). Has the ability to upload/download, version files.
  • CNS Image (An all-round plug-in for image handling.)
  • InsideScan (Scan directly into a container field.)
  • ExifPlugIn (Get EXIF data from pictures taken with a camera.)
  • ScriptMaster (Has basic functions for cropping, rotating, watermarking, etc.)
  • Theme Library (Themes, buttons, image manipulation)

Supported Formats for Container Fields

FileMaker Pro supports the following picture, QuickTime, and sound formats (Exhibit B)

FileMaker Supported Image Formats

General Image Suggestions

Print Quality: 300 DPI CMYK or Grayscale JPG or TIFF (if you need large, good-quality photos)

Screen Quality: 75 DPI RGB or B&W

Transparency: If you plan to use transparency, FileMaker suggests using TIFF, PNG, or JPG images. FileMaker does not recommend using the PICT (.pct) format with transparency.)

Caveats: For proper image handling, QuickTime installation is suggested on Windows.

Image Resizing and Cropping

The Preview app on Mac OS X can manipulate images: you can crop, resize, even convert them to a different format (JPG, GIF, PNG, TIFF, etc.) (Exhibit C).  Some plug-ins and the Theme Library can enhance your image manipulation experience.

Image Resizing in Preview

FileMaker Go

FileMaker Go has now the following functions for container fields (Exhibit D):

  • Choose From Library
  • Take Photo  (iOS device with camera required)
  • Get Signature
  • Paste
  • Open
  • Email

Container Field Options on FileMaker Go

SuperContainer works with FileMaker Go without programming changes. Because SuperContainer thumbnail file sizes are a tiny fraction of the full-size images, they load much faster, especially over a 3G connection.

* You can view any image that your browser (Safari on Mac and Internet Explorer on Windows) supports.


NJ FileMaker Developer Group Meeting Recap – 08/31/2011

We had our first monthly meeting after the FileMaker Developer Conference this year yesterday.

We moved to a new location:

Essex Computers
185 Rt 17 North
Paramus, NJ 07652
(201) 576-0001

The new location is cozy, there is a projector, the tables can be folded up so we can even dance (if we care to), but most importantly: it has WIFI (yippee). Also, on your way in or out you can pick up Apple computers or accessories from the friendly staff at Essex Computers.

We did a quick recap of Devcon to see what people though of it, what sessions they found interesting and the general consensus was that it is worth going to devcon, we liked the changes FMI implemented this year, but we could use more content next year.

We also assessed damage caused by Hurricane Irene among our members and luckily no major damage was done, aside from some basement flooding. Some folks are still without power and we wish them a speedy repair process. We also learned one of our member’s client was not so lucky and his office was flooded. He might not have luck with saving his hard drives and might not have backup.

Takeaway: We cannot emphasize enough: back up, back up, back up. If you have no server, back  your (closed) files manually into Dropbox or use Mozy or some similar service. If you have a server, use SafetyNet from 360 Works. The plug-in itself is free, all you have to pay for is the files you back up.  My SafetyNet backup cost me ~$5/month, so does Mozy. I also use Dropbox for manually backing up files I develop locally. Dropbox is not meant for hosting FileMaker files for multiple users. It is not a FileMaker Server. You can easily corrupt your files, aside from the fact that you can lose data.

We got two new members to the group: welcome Sharon and Drew. It was interesting to learn that form a room full of people only 1 person has a degree in computer science; the rest of us just picked up the trade on a job or by ourselves. Hope we didn’t intimidate the newcomers much and you will come again and again with questions and eventually suggestions and ideas.

The group is open to anyone whether you;re just getting your feet wet with FileMaker or are a seasoned developer. If you’re just generally lurking, please don’t be shy, come and join us. Join our Google Group for discussions, meeting reminders and more.

Thanks, Adam Aronson of Full City Consulting, for hosting the group and finding us a new home!