null Skip to main content

GF 107 - 1.5 Mil Opaque White Mounting Film, Clear High Tack Adh.

Item#Item NameRegular PriceSale PriceQty
GF 107 - 1.5 Mil White Opaque

GF 107 print mount film is a double-coated pressure sensitive 1.5 mil opaque white polypropylene film with clear acrylic high-tack permanent adhesive on both sides. GF 107 is a self-wound product using a 4.5 mil white 76# paper liner. This product is designed for laminating thin flexible films and papers. This opaque mounting film is laminated by the cold laminating process without the addition of heat.

APPLICATIONS
  • General Signage
  • POP & Indoor Signage
INK COMPATIBILITY
  • Not Applicable
 
What are the recommended applications for GF 107?
GF 107 is designed to mount photographic, digital, screen printed, and other printed images to a variety of opaque substrates such as Gatorfoam®, Fome-Cor®, and Sintra®. GF 107 may also be used with smooth painted metal and clean plastic substrates such as ABS, rigid vinyl and styrene. Since GF 107 is an opaque mounting film, it is not recommended for back lit applications. In all cases the substrates must be clean and free of dust, dirt and oil.
What if my substrate is dark or colored?
GF 107 is 100% opaque because of the double-sided white polypropylene film and is therefore ideal for darker substrates.
Free Local Delivery
Next Day Delivery
Order By 5PM CST
Save 2% On Pickup
Low Rate Financing
Flat Rate Shipping
Join Our Mailing List

Sign up to receive updates, special offers, and discounts!

// Uses React's native (unpatched) value setter + a real dispatched event, // so the app's own onChange / validation / append logic fires correctly. // build the visible field the user will actually type into // copy the real field's classes + computed styles so it looks identical // preload with existing value (formatted) if the real field already has one // hide the real field visually but keep it in the DOM and functional, // so your app's own validation / append event still works as before // place the visible field right where the real one used to be // send only the plain digits to the real field — this matches what // the numeric field type expects, so no "invalid phone number" error // keep focus/blur events flowing to the real field too, in case your // app's validation triggers specifically on those