null Skip to main content

GF 103 - 5 Mil Matte Clear, Clear Permanent Adhesive

Item#Item NameRegular PriceSale PriceQty
GF 103 is a 5.0 mil clear polycarbonate textured matte laminating film. This polycarbonate laminate has a clear permanent acrylic adhesive on a 1.5 mil polyester film liner. GF 103 offers protection from abrasion and moisture in interior applications. It is best applied by using a cold laminating process (heat is not recommended). GF 103 laminate is designed to protect digital image prints and screen-printed images for exhibit and display graphics. GF 103 can be used in most instances where a laminate with non-glare properties is required.
 

APPLICATIONS

  • General Signage
  • POP & Indoor Signage

INK COMPATIBILITY

Not Applicable

 

What types of applications is GF 103 good for?

This laminate can be used on graphics for flat, curved or rolled display applications. GF 103 is also ideal for protecting graphics on counter tops or frequent contact areas, or for adding rigidity and durability to graphics used in trade show displays.

Can I use GF 103 for a floor laminate?

No. Although GF 103 is textured, it is not rated for slip resistance.

Do you have any tips for keeping my graphic from curling?

GF 103 is designed as a cold laminate. If you experience curl and the tension on your pull rollers is minimal, try reducing the heat, reduce the pressure and reduce the speed of your take-up reel.

// 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