null Skip to main content

GF 118 - 1 mil Clear Mounting Film, Clear Perm/Remov. Adh.

Item#Item NameRegular PriceSale PriceQty

GF 118 is a double-coated pressure sensitive 1.0 mil clear polyester film with a permanent adhesive on one side and a removable adhesive on the other side. GF 118 has a two-liner construction. One side has a 1.2 mil clear polyester liner printed with “Remove to Expose Adhesive” to identify the removable adhesive and allows the graphics to be viewed after lamination. The other side has a 1.5 mil clear polyester liner for added clarity and wet out (permanent adhesive side). This product is designed for laminating thin flexible plastic films and papers commonly found in graphics for temporary application to glass. GF 118 clear mounting film can be laminated by a cold laminating process without the addition of heat.

APPLICATIONS

  • General Signage
  • POP & Indoor Signage
  • Windows

INK COMPATIBILITY

Not Applicable

 

How do I know which side to apply to the printed graphic?

The side that is opposite the printed liner side is the permanent adhesive side.
 

How do I know which side to apply to the printed graphic?

When you are finished applying the 118 film, you will have a graphic that will have the words “REMOVE TO EXPOSE ADHESIVE” on the face of the printed graphic. This is the side that is applied to the glass surface.
 

Is this product clear?

GF 118 has good clarity, but is not considered “optically clear”.

 

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