null Skip to main content

GF 106 - 1 Mil Optically Clear Mounting Film, Clear 2-Sided Permanent Adhesive

Item#Item NameRegular PriceSale PriceQty
GF 106 - 1 Mil Transparent Optically Clear

GF 106 mounting film is a double-coated pressure sensitive 1.0 mil polyester film with optically clear permanent acrylic adhesive. Two 1.5 mil polyester film liners are used to maintain excellent adhesive clarity. This clear mounting film offers protection from UV light, abrasion, moisture and other environmental exposures. This product is designed for laminating thin flexible films and papers under 10 mils in total thickness. It can be 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 106?

GF 106 is is designed to mount backlit transparencies to glass, Plexiglass or other clear substrates in light box applications. 106 also provides distortion-free face mounting of prints to these same clear substrates.
 

Do I need a laminator for this product?

Yes. GF 106 has two polyester liners (one on each side) to protect and ensure the optical clarity. A release liner take-up is necessary to process this product through typical laminators.

 

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