Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Polymorphic attachments with paperclip

branch: master

Fetching latest commit…


Cannot retrieve the latest commit at this time

Octocat-spinner-32 lib
Octocat-spinner-32 rails
Octocat-spinner-32 spec
Octocat-spinner-32 .document
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .rspec
Octocat-spinner-32 Gemfile
Octocat-spinner-32 Gemfile.lock
Octocat-spinner-32 LICENSE.txt
Octocat-spinner-32 README.rdoc
Octocat-spinner-32 Rakefile
Octocat-spinner-32 VERSION
Octocat-spinner-32 polypaperclip.gemspec


An adaptation of paperclip that uses a central attachments table so that you can attach many files to a given model without adding large amounts of database columns

class Page < ActiveRecord::Base
  has_attachment :primary_image, 
    :styles => {:large => "300x300", :thumb => "100x100"}
  has_attachment :secondary_image, 
    :styles => {:large => "200x200", :thumb => "50x50"}


Polypaperclip works with Rails 3 only.

Add polypaperclip to your Gemfile.

gem 'polypaperclip'

Generate the migration that creates the attachments table for you. The migration adds an index for optimized querying.

rails g polypaperclip:migration

Create config/paperclip.yml to override default paperclip options for different environments Credit: jspies

development: storage: s3 bucket: bucket-name s3_credentials: “./config/s3.yml” path: “public:url”

test: storage: s3 bucket: bucket-name s3_credentials: “./config/s3.yml” path: “public:url”

production: storage: s3 bucket: bucket-name s3_credentials: “./config/s3.yml” path: “public:url”

Performance Note

If you're going to be referencing these attachments in massive queries, don't forget:

Page.include(:primary_image_attachment, :secondary_image_attachment)

This will eliminate n+1 query situations which can adversely impact performance.


  • has_many_attachments

  • validations?

Special Thanks

Thanks to Coyne Design ( for granting MIT license to this gem.

Contributing to polypaperclip

  • Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet

  • Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it

  • Fork the project

  • Start a feature/bugfix branch

  • Commit and push until you are happy with your contribution

  • Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.

  • Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.


Copyright © 2011 Dan Pickett. See LICENSE.txt for further details.

Something went wrong with that request. Please try again.